Re : Inter company stock transfer through EDI

Question

Hi
      How to do the intercompany stock transfer through EDI. In this if Purchase order is created from one comapny a sales order should created automaticall in another Company. Fot this what is the SPRO settings.
How to do this.
Thanks
Anto

Answer 1

Hi,
continues from here,
Inbound file:     edi_in
Function module:     See text below.
Status file parameters
Directory:     /home/edi/<portname>/
Outbound file:     status.idoc
Function module:     Leave blank if using above
u2022     Both the portname and the exchange directory should be created according to the same naming convention. However, the portname should be in upper case whereas the corresponding directory name should be in lower case (see examples below).
     Portname (upper case):
                         <portname>
     Exchange directory name (lower case):           
                         /home/edi/<portname>
     where <portname> consists of:
     EDI<system name><client number><id char>
     <system name> is the name of  system on which port exists eg.      F01, PG1 etc.;
     <client number> is name of client on system which will use this      port; and
     <id char> is a single alphabetical character such as u2018au2019,u2019bu2019 etc.      typically,      u2018au2019 will denote dynamic outbound file naming (used      for testing) whereas      u2018bu2019 will denote static outbound file naming.      All ports will use static       inbound filenames.
For example, the name of a port using dynamic file naming on system F01, client 610 would be named EDIF01610A.  The exchange directory would be named edif01610a. Similarly, the name of port using static file naming on system PG1, client 600 would be EDIPG1600B. The exchange directory name would be edipg1600b.
Note that the function u201CEDI_PATH_CREATE_USERNAME_DT_TMu201D  can be used in the u201CFunction moduleu201D field  of the Outbound file parameters if IDocs are to be written to multiple files. In this case, the corresponding outbound filename field should be left blank. The standard IDoc exchange interface between the SAP EDI component and the EDI subsystem uses a single file for each transfer direction. However, should the exchange interface change, or for testing purposes, the function modules for dynamic naming can be used.
2.4.2.     Control of EDI processes in R/3
2.4.2.1.      Maintain: Outbound Process Code (WE41)
IMGCross-Application ComponentsALE Extensions  Outbound
Check that the outbound EDI processes in the R/3 system are defined.  Indicates which ABAP/4 function module to execute in order to create an outbound IDoc.
The following assignments are available for R/3:
2.4.2.2.      Maintain: Inbound Process Code (WE42)
IMGCross-Application Components  ALE  Extensions  Inbound
Check that the inbound EDI processes in the R/3 system are defined.  Indicates what kind of inbound processing to execute.
     A long list of options is available under Processing by function module, relevant ones are:
INVF     INVOIC FI     Invoice receipt (Financial Accounting)
INVM     INVOIC MM     Invoice verification (Mat Management)
ORDC     ORDCHG     Change customer order
ORDE     ORDERS     Create customer order
ORDR     ORDRSP     Purchase order confirmation
2.4.2.3.      Control: System Process Codes (WE40)
     Choose Processing by task.  Check that the codes indicating the type of EDI processing error are defined.  The only valid entries are the entries shown on the screen, as they are directly called via the EDI basis module.
2.4.2.4.      Control: Status maintenance (WE47)
     Check that the codes indicating status of IDoc processing are defined.  The status values for outbound IDocs are between 01 and 39, while the status values for inbound IDocs begin with 50.  These values are delivered by SAP and cannot be customised.
2.4.2.5.      Control: Partner Types (WE44)
     Check that the codes that identify the commercial relationships between the receiver and sender are defined.  Values are delivered by SAP.  Names of the programs and routines that validates the entry of the EDI trading partner ID:
Partner type     Report name     Form routine
B - Bank     RFETESTP     READ_T012
KU - customer     RSETESTP     READ_KNA1
LI - vendors     RSETESTP     READ_LFA1
LS - logical system ( ALE)     RSETESTP     LOGSYS
2.4.2.6.      Control: Forward Inbound (WE45)
Allows for the forwarding of IDocs to a specific application.  Contains the exactly defined destination of an inbound IDoc within the SAP system.  Usually no changes are required.
2.4.2.7.      Control: Status Process code (WE56)
Choose Processing by task: The following set-up has been provided as default:
Process code:     EDIS
Identification:     TS30000078
Description:     EDI-IDoc  status record processing
The process code is for inbound status, The ID type is an identification code for inbound processing method (workflow or standard task) of the status record.
3.     MM IMG CONFIGURATION
3.1.     Global settings (IMG):
3.1.1.     Units of measure (IMG  Global settings):
The ISO code is important for EDI.  It is used to convert the internal SAP units of measure into standard units.
The MM configurer must link the Unit Of Measure, EACH, with the ISO code PCE (Piece).
3.2.     Link Schema to Purchase order
Check the following:
IMG  MM  Purchasing  Message determination  Message determination  Message Schemas
Execute transaction u201CDefine Message Schemas for Purchase Orderu201D
Select  transaction: Assign Schema to purchase order
Add:      Usage =B for output
     Application = EF for purchase order
     Procedure = RMBEF1 for purchase order
3.3.     Link application to EDI interface via message control:
IMG  MM  Purchasing  Messages  Output Control
Check following under Output Control:
     Condition table
     Access sequence
     Message types
     Message schema
     Output control
3.4.     Enabling Multiple Output for Purchase Orders (Optional)
For example: EDI & Printing
IMG  MM  Purchasing  Message determination  Message determination Access sequence
u2022     Create new access sequence (e.g. ZPUR), copy the access sequence 0001 but leaving the ''E'' flag blank (Exclusive is off). (Transaction M/50)
u2022     Goto Define message types  maintain message types:
     Create a new message type (e.g. NEU1), setting the output type to 1 for printed output and using ZPUR as access sequence. (Transaction M/34)
u2022     Goto Message Schema  define message schema  maintain output determination procedure:
     Update procedure RMBEF1 by adding a step for the new condition type (e.g. NEU1) prior to the standard delivered step for NEU. (Transaction M/36)
u2022     Goto Processing program  Define Processing program  Output program: Purchase Order.
     - Add a NEU1 record to table TNAPR.  The program FORM Routine and layout must be specified.  (Copy an existing NEU record). (Transaction OMTB)
u2022     Goto Processing program  Define Processing program  Output by partner type.
     - Add NEU1 record for VN (vendor). (Transaction OMTG)
3.5.     Link Output type (fax=2, E-mail=7) to NEU (Purchasing)
IMG  MM  Purchasing  Message determination  Message determination Access sequence
u2022     Goto Processing program  Define Processing program  Output program: Purchase Order.
     - Add another NEU record to table TNAPR with the appropriate output medium. Copy an existing NEU record. (Transaction OMTB)
u2022     Goto Processing program  Define Processing program  Output by partner type.
     - Add NEU record for VN (vendor). (Transaction OMTG)
4.     SD APPLICATION REQUIREMENTS
Assumption: SD is only used for testing purposes and configuration is based on a need basis - only configure the minimum.
Reference SAP Course manual Chapter 11.
4.1.     EDI Configurations
4.1.1.     Conversion of SAP item categories to IDOC item categories (VOE1)
IMG  S&D  EDI  EDI Messages  Conversion of SAP item categories to IDOC item categories
Add the following entry:
For Standard Item description :     0     OR     LDN
Typically error message: ''Transaction LDN is not defined".
4.1.2.     Partner functions
IMG  S&D  EDI  EDI Messages  Configure EDI Partners Partner  Application  Partner function
Check that the following partner functions exist: (at least)
SP     Sold-to party
VN     Vendor
BP     Bill-to party
SH     Ship-to party
Note - the German abbreviation is passed to the IDoc.
4.2.     S&D Sales Configurations
4.2.1.     Maintain Item categories
IMG  S&D  Sales  Sales document  Sales doc item  Define item categories
Add LDN for standard item:
          Item type = B
          Relev for billing = B
          Tick following:     Bus data item
                              Sched line allowed
                              Credit active
                              Pricing
          Screen seq. grp = N
4.2.2.     Assign Item categories
IMG  S&D  Sales  Sales document  Sales doc item  Assign item categories
Add/Update the following entries:
     1     2     3
Sales doc type     OR     OR     OR
Item category group     NORM     DIEN     LEIS
Item category     LDN     TAD
LDN     LDN
4.2.3.     Assign Schedule line categories
IMG  S&D  Sales  Sales document  Schedule lines  Assign Schedule line categories
Add Item category LDN to table (with no other parameters).
4.3.     S&D Pricing Configurations
4.3.1.     EDI pricing condition types
IMG  S&D  Basic functions  Pricing  Pricing control  Define condition types  Maintain condition types
Maintain the following condition types:
     EDI 1 - Calculate type =C for Quantity
     EDI 2 - Calculate type = B for Fixed amount
4.3.2.     SD Pricing procedures (V/08)
IMG  S&D  Basic functions  Pricing  Pricing control  Define & Assign pricing procedures
Maintain pricing procedure for ZVAA01 (Standard). 
Select control and add EDI1 and EDI2  as steps 1 and 5 respectively with no other parameters.
5.     INVOICE IMG CONFIGURATION
No additional IMG configuration (not partner specific) was needed for Inbound Invoice processing.
Thanks,
Swamy H P