Idoc example link - useful

https://www.egger.com/downloads/bildarchiv/88000/1_88047_IT_DESADV_SAP_IDOC_XML_Lieferant_EN.pdf

List of Inbound and outbound Idoc user-exits

http://sapist.blogspot.co.uk/2015/07/list-of-inbound-and-outbound-idoc-user.html

Inbound Idoc extension

WE31 - To create custom segment
WE30 - To create extension

WE82 - To do mapping

WE57 - Assign new extension to Function module.

In incoming idoc, extension should be given in CIMTYP  - while using WE19, give in CIMTYP of control record (header)

Above setup is enough for inbound extension - No setup needed in partner profile to include extension (you however need to include process code)

Invoice verification (MIRO) - INVOIC
basic type: INVOIC02
extension: ZINVOIC

Idoc Links

Invoice verification (MIRO) Inbound Idoc

INVOIC02

http://help.sap.com/saphelp_di46c2/helpdata/EN/44/f50abfea3b11d194dc0000e83dd751/content.htm

Trigger idoc on change of customer data

For the automatic transfer of master data ,we can use change pointer technique.

Following are the steps to be followed:-

1) Enable change pointer globally (t.code BD61).

 

2)Enable Change Pointers for a Message Type (t.code BD50).

Here you have to check the Active checkbox corresponding to customer master message type 'DEBMAS'.

 

3)Specify the Fields for Which Change Pointers Are to Be Written (t.code BD52).

Various number of fields are present here corresponding to message type'DEBMAS'. If you want to add any other field , you can add here.

 

Apart from above three settings, all other ALE configurations are required like( partner profile, distribution model etc.) Eg: SALE tcode, setup distribution model

 

For triggering the Idoc program 'RBDMIDOC' should be scheduled.

When you make any change in the customer master , Idoc will be triggered automatically from your SAP system.

Order Idoc - to pass Text id

Please fill following in idoc to give EAN number in Text field in SAP.

E1EDP01-POSEX = item number (start with 1 and continue sequence numbers for all items)

 

E1EDPT1-TDID = 'ZCEA' and TSSPRAS = 'E' and

E1EDPT2-TDLINE = EAN number  -  and E1EDPT2- TDFORMAT = * (asterisk)

EDI Idocs tips

How to retransmit multiple idocs:

Dropbox -> CMS -> EDI Idocs -> 'How to retransmit multiple idocs'

Set up EDI Idoc (Custom)

WE30 - To create basic type (or Extension) of custom idoc

WE31 - To create segments - with fields - Once you create you set them 'Release'

WE81 - Define Message type  -

WE82 - Link message type with idoc type


Outbound Idoc (Custom) -
- In Partner profile in WE20 set this new idoc type for the partner you want to sent to (like Logical System (LS) or Customer etc)

- Create a function module using FM MASTER_IDOC_DISTRIBUTE .  Take reference of MASTERIDOC_CREATE_* functions.

- Use the above function in your program to trigger idocs

 

Program to change status of Idocs

Program to change status of Idocs (for eg: in case you want to 'archive' and make them Green) :

RC1_IDOC_SET_STATUS  - You can set status to 71 (archive) - Idocs turn Green after the status is set.

EDI Output - 'change' output

To send EDI Idocs for any changes to document:

For eg, Output type ZEDI
Set program-routine in Output type config (in NACE) to define what the change mean. for eg, SAPMV45A-ZZCHECK_CHANGE (keep condition on partner profile table - for EDI - as we dont want to unnecessarily trigger for which partner prof setup is not maintianed - otherwise change output gets triggered but goes into error, as there is no message type set.

Then set Partner profile - tick 'Change' box and give which message type the change idoc should go.

 

Idocs reciever port determination

Reciever port for outbound idocs can be determined from
1) Distribution model (in SALE tcode) - where  message type is assigned to reciever's Logical system (LS) which is assigned to sender's LS
2) From Partner profiles (WE20), where recieving port determined from Partner (KU, LS, etc).
 

Setup EDI idoc (Standard)

How to setup new EDI idoc (Standard)

Step 1:  Find relavant Idoc type and Message type - This is based on business process.
Dropbox -> CMS -> EDI Idocs -> 'EDI with EDIFACT - Mapping Types' doc can help  - Or just search in internet

Step 2: Go to WE19  - > Get template for Test based on Messag type

Step 3: Get an idea on what to fill in template using WE60 tcode (look for Documentation)
You can also find XML templates in internet for message type.

Step 4: Run and make sure it works.  Now, note down if you require any additional fields.

 

EDI Idocs files

Path:  Dropbox -> CMS -> EDI Idocs

EDI Tcodes

WEDI - Area menu for EDI relavant tcodes

WE05 - Idoc List
WE19 -  Test tool for Idoc processing - you can run FM in foreground and debug (take an existing idoc and run it)
WE09 - Search Idocs for Business content (you can search for a field value) - You can change field values here and save (which then can be reprocessed using BD87/84)

WE20 - Partner profiles
WE60 - Mapping Structures/Documentation 

WE21 - Ports definition in Idoc processing  (setup SAPPI_PRD port here )

SALE - Idoc Interface ALE settings (setup distribution model, logical sys etc here)

WE30 - Develop idoc types
WE31 - Develop idoc segments

WE57 - To setup FM <-> Message type assignment
WE41/WE42 - Process codes

BD84 - Reprocess Idocs
BD87 - Status monitor

RSEOUT00 - Process all Selected Idocs (for Partner) - This way you can collect all Idocs for a partner and send them at a time.

VOE2 - To map customer to Sales area and Order type
VOE4 - To map customer ship-to (external) with internal number  (We dont want our customer to remember all the ship-to numbers.. do we?)

IDOC -  Idoc and EDI basis

Vendor to Us(our comp) mapping (for INVOIC type - vend invoice):
OBCA - Map vendor company code to our real company code
OBCD - Map External tax rate to Tax code
OBCE - EDI INVOIC Programming parameters