cancel
Showing results for 
Search instead for 
Did you mean: 

Intercompany Billing - Automatic posting to vendor account

Former Member
0 Kudos

Hi all,

Can any one explain how the Intercompany Billing - Automatic posting to vendor account works?

Say for example: supplying plant- 1000

Recieving sales plant- 3000

Customer- 13000

Vendor- 14000

For this data, if I post a billing from sales org 1000, how do I check whether it is posted to vendor side?

My process is STO-replenishement delivery-Billing

Kindly help.

Regards,

Beena

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

This can be handle by using an user exit, which will call T.Code to creating accounting document for the vendor, as soon as the Billing document is saved.

You will have to get it designed as per the requirement of the client.

Regards,

Rajesh Banka

Former Member
0 Kudos

Hi Beena!

Go through following help doc.

Automatic Posting To Vendor Account (SAP-EDI)

In this activity, you set up automatic posting to vendor account for intercompany billing with SAP-EDI direct to financial accounting.

EDI outbound processing for intercompany billing links to EDI inbound processing for invoice receipt in FI and posting to vendor account is carried out in the selling company code.

prerequisites:

Before making the settings in Customizing you must create a vendor master record that represents the delivering company code. This vendor master record must be created in "Selling company code".

You also need an output condition record (transaction VV31) for output type "RD04" and the customers for intercompany billing.

Customizing settings:

1. Message type:

Message type RD04 is set for posting to vendor account in intercompany billing. (TA:V/040)

2. Message determination procedure:

Message determination procedure V40000 is valid for billing type IV.

3. Message control:

In the administration of EDI processing, a partner agreement must be defined for message control of inbound and outbound processing, since sender and receiver data are needed. The outbound process code is used to initiate a function module version 5 (function module version 3.0 for initiating inbound processing).

Process code outbound: SD08.

For further information on settings for messages, see the IMG section "messages".

4. Outbound processing:

a) Partner agreement (transaction WE20)

Partner number : Specify customer number IV

Partner type : KU

b) Message controlling:

Partner number : Customer number IV

Partner type : KU

Partner role : RE

Application : V3

Message type :RD04

Message:

Message category:INVOIC

Message variant: FI

Outbound options:

Outbound code : SD08 INVOIC Intercompany billing,

c) Outbound parameters:

Outbound options:

Receiver port : e.g. SAPP30 EDI MM development

IDoc cat. : INVOIC01

Basis IDoc cat. : INVOIC01

5. Inbound processing (transaction SBPT) for customer

a) Inbound parameters:

Partner number : Specify vendor number

Partner type : LI

Partner functions:

Message category : INVOIC invoice / billing document

Output variant : FI

Process code :INVF

6. Check assignment of process code and processing function modules.

Transaction: WE42 >>Basis >> Control>> Process code inbound >> Processing with funct. modules>>With or w/o ALE

Code :INVF

Identification:idoc_input_invoice_fi (INVOIC FI invoice receipt)

or

code FI03 up to 3.0E

Identification:idoc_input_invoice_fi

7. Vendor:

A vendor must be assigned per company code and customer for intercompany billing (transaction WEL1)

Example:

Data:

Delivering company code: 0001

Customer: 0000000001, created in delivering company code

Selling company codekreis: 0099

Vendor: ALECRED01, created om selling company code

Settings:

Application: V3

Logical address 00010000000001

is made up of:

a) 4 place delivering company code : 0001

b) 10 place customer number : 0000000001

Target:

Company code: 0099

Vendor : ALECRED01

Note

The logical address must contain 14 digits. If the customer number does not contain 10 digits, zeros must be put before it.

If the logical address is not correctly maintained in table EDILOGADR, error message: " Company code could not be determined for intermediate document XXXXX" appears.

8. Account assignment:

You can set an indicator that determines whether account assignments are to be copied from the customer billing document during creation of posting to vendor account in the selling company code

This affects the following account assignments:

9. Projects

10. Profit center

11. Cost center

12. Profitability segment

Former Member
0 Kudos

Hi Shiva and Rajesh

Thank you for taking time to reply. Rajesh, do you know which user exit to use?

Shiva,

I cross checked my setting with the help you provided and it is the same. To test I created an invoice and checked it using WE05, getting status 51 with error, ISO code PCE not assigned. Infact I used different material to test I get the same error for all the unit of measure. In transaction CUNI, the ISO code have been assigned to the base unit of measure. Any idea why I am getting this error?

Regards,

Beena