Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
Showing results for 
Search instead for 
Did you mean: 
I would like to share with you another update on the B2B Library content included in the SAP Integration Advisor offering:

  • As a new offering you will now find the GS1 Global Codelist collection in the newest available version. More details will be provided as part of this blog post.

  • We have published the newest versions 1.2.054 and 1.2.055 of cXML.

  • We have included the latest version for ASC X12 (008030).

The picture above depicts the overall building blocks of Integration Advisor. This blog post mainly relates to the Type Systems (B2B Library) area.

B2B Libraries in SAP Integration Advisor

SAP Integration Advisor provides you with the Message Definitions and Codelist collections for frequently used B2B Message Standards.

Our offering currently includes the predominantly used B2B Standards ASC X12 and UN/EDIFACT plus cXML, EANCOM and Odette as well as the Automotive EDIFACT subsets (from the organizations JAIF, Odette and VDA). Based on these standard definitions, you can create and maintain your own customized Message Implementation Guidelines (MIGs) and implement Mapping Guidelines (MAGs).

The application also offers frequently used Codelists like the ISO Codelists, UNCEFACT Codelists and Automotive Codelists (from JAIF, Odette and VDA). You can use these codelists to make the specification of your MIGs even more descriptive.

You can find all this predefined content in the Library of Type System section of the Integration Advisor.

GS1 Global Codelist collection in Integration Advisor

The GS1 organization provides numerous codelists for different domains (EDI, for example). According to GS1, a codelist is a standardized list of values allowed at a given location of a GS1 EDI message. GS1 tries to use international standard codelists whenever possible. GS1 develops its own code lists only if no suitable international standard exists. For more background on the GS1 Codelist philosophy you can refer to the GS1 homepage (Link).

Integration Advisor now offers the GS1 Codelists relevant for the EDI domain that can be used in GS1 EDI messages.

You can find this codelist collection as a new entry GS1 Codelists in the Library of Type System section. It contains 211 codelists that are provided as part of the newest available version from May 2021:

You can use these codelists in any Message Implementation Guideline (MIG), particularly for MIGs based on GS1 messages. Currently this applies to GS1 EANCOM. And in future this will also be of interest in the context of GS1 XML which is on our roadmap for next year.

A few content details

Each GS1 Codelist has a name defined by the GS1 organization, for example AdministrativeUnitTypeCode. The majority of these codelists are developed and maintained by GS1.

GS1 EDI messages also use international standard codelists from organizations like ISO and UNCEFACT. Although GS1 defined its own names for them, they often only refer to the international standard codelists and GS1 does not list the actual code values. For example:

  • ISO: CurrencyCode (ISO 4217), LanguageCode (ISO 639-1), CountrySubdivisionCode (ISO 3166-2),

  • UNCEFACT: IncotermsCode (Rec 5), MeasurementUnitCode (Rec 20), TransportInstructionStatusReasonCode (Rec 24).

If such a standard codelist was unchanged by GS1 (= fully adopted), then it is not included in the GS1 Codelist collection in Integration Advisor. Instead you can simply use the according ISO or UNCEFACT codelist directly.

Sometimes GS1 has extended or restricted international standard codelists. For example:

  • ISO: CountryCode (ISO 3166-1) = a few special values defined by GS1

  • UNCEFACT: TimeMeasurementUnitCode and TemperatureMeasurementUnitCode are use-case specific restrictions of Rec 20, while PackageTypeCode is an extension of Rec 21.

Such modified codelists are included in the GS1 Codelist collection and can be found under their GS1 names.

In a similar way, GS1 has extended and/or restricted a number of codelists from UN/EDIFACT. For example:

  • AllowanceChargeTypeCode based on UN/EDIFACT DE 5189 - extended by GS1,

  • PaymentTermsTypeCode based on UN/EDIFACT DE 4279 - restricted by GS1,

  • OrderTypeCode based on UN/EDIFACT DE 1001 - restricted and extended by GS1.

These codelists are also part of our GS1 Codelist offering under their GS1 names. There are a handful of UN/EDIFACT codelists that have their own GS1 name although they were unchanged by GS1 (fully adopted) - for simplicity they are also part of the GS1 Codelist package.

Further reading