IDoc/X12/EDIFACT relationship

Here is a table which describes IDoc to X12/EDIFACT relationship. I believe it was originally published by Emmanuel Hadzipetros, the author of “Architecting EDI with SAP IDocs”. Now I see it all other the Internet.

I’ve been using it a lot and find it extremely useful:

Inbound Interfaces

MsgType BasicType Description EDIFACT X12
ACLPAY ACLPAY01 Freight invoice INVOIC 210
CREADV PEXR2002 Credit advice CREADV 812
CREADV PEXR2002 Extended credit advice CREEXT 812
CREADV PEXR2002 Multiple credit advice CREMUL 812
CREMAS CREMAS04 Vendor/Org info PARTIN 816
DEBADV PEXR2002 Debit advice DEBADV 812
DEBADV PEXR2002 Multiple debit advice DEBMUL 812
DEBMAS DEBMAS06 Customer/Org info PARTIN 816
DELFOR DELFOR01 Delivery schedule DELFOR 830
DELINS DELFOR02 Delivery schedule DELFOR 830, 862
DELJIT DELFOR01 Just in time delivery DELJIT 830, 862
DELORD ORDERS05 Delivery request ORDERS 830, 850
DESADV DELVRY03 Delivery (Despatch Advice) DESADV 856, 940
DIRDEB PEXR2002 Direct debit DIRDEB 828
DIRDEB PEXFI03 Direct debit DIRDEB 828
FINSTA FINSTA01 Financial statement FINSTA 821, 822
GSVERF GSVERF03 Credit memo procedure ORDERS 861
IFTMIN SHPMNT04 Forwarding order IFTMIN 204, 304
INVOIC INVOIC02 Vendor Invoice INVOIC 810, 880
MBGMCR MBGMCR03 Post Goods Mvmt & PGI Del RECADV 856, 867, 945
MBGMCR MBGMCR03 Goods Mvmt & Goods Receipt PO RECADV 867, 944
ORDCHG ORDERS05 PO Change Request ORDCHG 860, 876
ORDERS ORDERS05 Customer PO ORDERS 850, 875
ORDRSP ORDERS05 PO confirm ORDRSP 855, 865
PAYEXT PEXR2002 Extended payment order PAYEXT 820
PAYEXT PEXR2002 Multiple payment order PAYMUL 820
PAYEXT PEXR2002 Payment order PAYORD 820
PROACT PROACT01 Inventory Report INVRPT 846, 852
PROACT PROACT01 Sales forecast SLSFCT 852
PROACT PROACT01 Sales report SLSRPT 852
REMADV PEXR2002 Credit advice CREADV 820
REMADV PEXR2002 Payment advice REMADV 820
REQOTE ORDERS05 Response to request for quotation REQOTE 840
SDPICK SDPIID01 Pick/Ship confirm & PGI RECADV 856, 867, 945
SHPADV SHPMNT05 Advanced Ship Notification SHPMNT 856
SHPCON DELVRY03 Ship confirm/PGI RECADV 856, 867, 945
SHPMNT SHPMNT05 Advanced ship noticifaction SHPMNT 856
SHPORD DELVRY03 Delivery despatch order DESADV 830, 850, 856, 940
STATUS SYSTAT01 Acknowledgement CONTRL 997
STATUS SYSTAT01 Functional acknowledgement FUNACK 997
TXTRAW TXTRAW02 Error report (text msg) APERAK 824, 864
TXTRAW TXTRAW02 Error report (text msg) GENRAL 824, 864
WHSCON DELVRY03 Stock confirmation & PGI RECADV 856, 867, 945
WHSORD DELVRY03 Delivery stock order DESADV 940
WMTORD WMTOID02 Transport request (goods movement) RECADV 856, 867, 945
WMMBXY WMMBID02 Post goods receipt (goods movement) RECADV 867, 940, 945

Outbound Interfaces

Continue reading

Sterling GIS/SI: problems with the disk space

A post about the Backup Service – again. If your GIS/SI saves archive data on disk and you do not clean it up from time to time, one day you might run out of space on this disc, Backup Service will stop working (“Error running backup”) and you might get a bunch of problems I described before. To prevent it you should control the archive folders and delete them from time to time.

First of all, you should know where these folders are located. Go to Operations > Archive Manager > Configure Archive Settings in the Dashboard and check Backup Directory setting:backup_disk_problem

If you open this directory, you’ll see a lot of subdirectories with the names in YYYYMMDD format, or something like this. You actually don’t need them all, especially the old ones (I would say the ones which are 2+ months old). So, you can move them to another disk and then delete the old directories. Or, you can simply delete all the old directories – you don’t need them in 99.99% cases. Some people think that they could use these backups for a Disaster Recovery, but it’s not true – they contain detailed information mostly from CORRELATION_SET, WORKFLOW_CONTEXT and so on. So, usually 2 months later you don’t need them (I hope your BPs save all the I/O documents separately?)

So, if you’re running out of space, you should delete the old directories and create some kind of a scheduled job which will be deleting old directories from time to time – to keep the system nice and clean.

Gennady Kim