SAP Reference Document Type Codes

Just for the reference

Codes used in SAP TM in BaseBusinessTransactionDocumentReference TypeCode

Document Type for Business Transaction Description
001 Purchase Order
114 Sales Order
1122 Transportation Order
58 Delivery number (Inbound delivery)
610 Shipper Booking Reference
614 Freight Order
618 Freight Unit
629 Freight Settlement Document
630 Forwarding Settlement Document
72 Opportunity (??)
73 Outbound Delivery
OPPT CRM Opportunity
RPO Returns Purchase Order
RSTO Returns Stock Transport Order
SSL45 Customs Invoice
STO Stock Transport Order
T50 Bill of Lading
T51 House Bill of Lading
T52 Master Bill of Lading
T53 Air Waybill
T54 House Air Waybill
T55 Master Air Waybill
T56 Reference number of Ordering Party
T57 Reference number of Shipper
T58 Reference number of Consignee
T59 Cancelled MM Invoice
T60 Subsequent Credit Memo
T61 Subsequent Debit Memo
T62 Cancelled Credit Memo
T63 Reference to Export Document
T64 Cancelled Billing Document
T67 Carrier PRO (Carrier Reference No.)

Continue reading

How to read X12 specifications

This article is about reading and understanding typical ANSI X12 specifications, generated with tools like SpecBuilder in PDF or MS Word format. Usually specifications are straight-forward, but there are some nuances you should be aware of.

An X12 specification is a particular implementation of X12 transaction, defined by a company to be used with its partners.

Prerequisites: you should be familiar with X12 components, such as transactions, loops/groups, segments and elements.

1. Cover Page

Often (but not always) it starts with a Cover page which contains X12 transaction set number (such as 850 for Purchase Order or 810 for Invoice), version, publication date, author, logo and some other things.

001 cover

The most important information is Transaction Set number (856 on the picture above) and X12 version (4010). Also I usually check the publication date to make sure it is not too old – if it is from 1990s, I would probably ask if it is the latest version.

Continue reading