Sap movement type for intercompany transactions

SAP MOVEMENT TYPE FOR INTERCOMPANY TRANSACTIONS VERIFICATION
SAP MOVEMENT TYPE FOR INTERCOMPANY TRANSACTIONS CODE

NOTE: You cannot use output type RD04 again therefore you must copy it in customizing to another output type (in this case RD00)

SAP MOVEMENT TYPE FOR INTERCOMPANY TRANSACTIONS CODE

in this case enter MM in 'message code field.ДЄs you can see the only difference between the FIВ and MM invoice is in the message code and output type.

SAP MOVEMENT TYPE FOR INTERCOMPANY TRANSACTIONS VERIFICATION

You can repeat the process for cases where invoice verification is done against purchase order. Go to the Message Control tab press and enter the data as specified in the following screen. Press enter and the screen will change to the following: BP Message type INVOIC Message Code FI Receiving port A000000001 Basic Type INVOIC01 Section, to maintain detail screens The following screen will appear.Д®nter the following data in the appropriate fields: Partn.funct. Code WE20)Д¬ustomer: Put cursor on Partner type KU and press create. Creating a Partner Profile for both CustomerВ and Vendor Tools a Business Communication -> IDoc Basis -> Idoc -> Partner Profile (T. IMG: Sales and Distribution -> Billing -> Intercompany Billing -> Automatic Posting To Vendor Account (SAP-EDI) -> Activate account assignment.Д¦. It is also necessary to activate the account assignment. The Logical address is completed when the receiving Company Code and the Vendor are entered in the detail screen. It was created just for this documentation and was not saved) (In our case the customer is an alpha numeric number so the second line was not necessary. if the customer number was 3100, than the logical address would have been 1180 000000 3100 as can be seen in the second line. Note: If the receiving Customer is a numeric number you must add zeros between the Company code and Customer number so the Logical Address will be 14 digits. Logical address 1180P3100 is made of the supplying Company Code (1180) and the receiving Customer (P3100). Create Logical Address IMG: Sales and Distribution -> Billing a Intercompany Billing -> Automatic Posting To Vendor Account (SAP-EDI) -> Assign vendor.

Master Data Maintain output Master Data Logistics -> Sales and Distribution -> Master Data -> Output -> (T. Sales and Distribution -> Basic Functions -> Output Control -> Output Determination a Output Determination Using the Condition Technique -> Maintain Output Determination for Billing Documents. Output type RD04 is maintained: IMG: Sales and Distribution -> Basic functions -> Output control -> Output Determination -> Output Determination Using the Condition Technique -> Maintain Output Determination for Billing Documents a Maintain Output Types (T. Output Type RD04 - Invoice Receipt MM is a special function, responsible for the execution of the Idoc and will be entered in the Partner Profile later on. Port name: Automatically generated Version: 4.x RFC destination: PLD (This was defined by the basis people). A dialog box will open asking whether you want the system to generate an automatic name or whether you wish to use your own name. Code WE21) Maintain Transactional RFC: (Choose Transactional RFC and press the create icon). Creating a Port Tools a Business Communication a IDoc Basis a Idoc a Port Definition (T. Vendor representing the supplying Company Code: P1180 NOTE: There is NO need to 'connect' vendor to customer in the control screen.ДЈ. The organizational data in this case is the same as above. Note: The Vendor is created in the receiving Company Code. The Vendor is created with the standard transaction (XK01). Creating a Vendor to represent the supplying company. The organizational data in this case is: Supplying Company Code: 1180 Supplying Plant: 1180 Supplying Sales Organization: 1180 Supplying Distribution Channel: 01 Supplying Division: 00 Receiving Company Code: 3100 Customer representing the receiving Company Code: P3100Дў. Note: The customer has been created in the supplying company code. The customer has already been created (XD01) for the purpose of Intercompany processing and entered in the appropriate transaction in customizing (Sales and Distribution a Billing a Intercompany Billing a Define Internal Customer Number By Sales Organization).

Creating a Customer to represent the receiving Company. The relevant FI customizing is maintained.ДЎ. The relevant MM customizing is maintained.ДЁ. Creating a Partner Profile for both CustomerВ and VendorД§. Creating a Vendor to represent the supplying company.Д¦. Creating a Customer to represent the receiving Company.Дў. In our case where both companies are processed in the same system (& client), it is sufficient to create Idoc. Inter-Company Billing - Automatic Posting To Vendor Account (SAP-EDI)ДЄutomatic posting to vendor account is done by EDI.

Sap movement type for intercompany transactions