on 08-03-2015 3:36 PM
Dear Gurus,
In order to make Rouble payments in Russia, we are required to provide a "VO code" as defined in the link below
http://www.seb.ee/sites/default/files/web/files/ruruahbyb/rur_tehingukoodid_072004_eng.pdf
I've browsed SCN and searched SPRO but found no information on how we can maintain "VO codes" in SAP. Please advise. Thank you!
This message was moderated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Alex,
VO Codes must be included as Payment Document specific field.
Please note that this must not be maintained as Vendor Specific because the vendor can transact in multiple ways.
VO Codes are applied depending on transaction. (Resident - Non-Resident)
1 accounting document = 1 Transaction.
Example:
Vendor can have different types of VO Code.
1 invoice for Vendor XXXXXXX with VO Code 2012000.
2 invoices for same vendor with VO Code 1001000.
It varies depending on the transaction.
You will need an ABAPer assistance to change the enhancement of Payment Program (F110).
Steps:
1. Users can input the respective VO Code while creating the document.
example: Input he VO code in Reference or Xref Fields of document header.
2. In Payment Program, coordinate with your abaper and customize the program to group invoices and credit memos based on same VO Codes:
3. Grouping: Company Code > Vendor > Currency > VO Code.
4. You will need to include this VO Code field into the IDOC that will be sent to the Bank.
5. You will also need to check with the receiver bank if their system can handle the new segment from the idoc that holds the VO Code value.
Hope this can help you.
Thanks,
Jayrold Vicencio
**
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Jayrold thank you for your suggestions. I was hoping that there is a standard functionality available through ECC for us to be able to configure the VO code determination or selection systematically, but looks like yet another custom built for a function that should naturally be available in the global ERP system
User | Count |
---|---|
100 | |
11 | |
10 | |
6 | |
6 | |
5 | |
4 | |
4 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.