Enterprise Resource Planning PortalERPGenie.COMEnterprise Resource Planning Portal

   Advertise | BLOG

Web ERPGenie.COM

Home | Vote for us |

 Sign up for PayPal and start accepting credit card payments instantly.

ERPGenie.COM -> NetWeaver -> Process Integration -> XI (Exchange Infrastructure) -> XI Naming Conventions

Software Component

SAP_<SID>

where <SID> is the system ID if the applicable system

Software Component Version

X.X

shows the applicable version as of this date. Eg. SAP_ECC is at version 5.0

Namespace

http://ERPGenie.COM/xi/<SCENARIO>/<SID>

where scenario refers to the interface being developed for and <SID> is the component where that object has relevance. Eg. http://ERPGenie.COM/xi/OrderOutput/ECC will contain all the objects relevant to the Order Output scenario in the ECC system.

Interface Objects

Message Interface

MI_<meaningful name>_<IN/OUT/AB>

where:

IN = Inbound

OUT = Outbound

AB = Abstract (For BPM)

Remember to evaluate the IN and OUT based on the point of view from the source system to the target system. Eg. If we send an XML message from xEXTERNAL to an IDoc in ECC, then the XML Message is an OUT and the ECC is an IN interface.

Message Type

MT_<meaningful name>

Fault Message Type

FMT_<meaningful name>

Data Type

DT_<meaningful name>

Data Type Enhancements

DTE_<meaningful name>

Context Object

CO_<meaningful name>

External Definition

ED_<meaningful name>

Mapping Objects

Message Mapping

MM_<meaningful name>_<source type>_<target type>

Eg. MM_ORDERSCENARIO_ORDERS05_OrderXML

Interface Mapping

IM__<meaningful name>_<source type>_<target type>

Eg. IM_ORDERSCENARIO_ORDERS05_OrderXML

Mapping Templates

MT__<meaningful name>_<source type>_<target type>

Imported Archives

IA_<meaningful name>

Services

Business Systems

SAP<SID>

Where <SID> is the relevant system ID number

E.g.. SAPECC, SAPCRM, SAP46C

Business Services

SRV_<XXXXXX>

Where XXXXXX is up to 6 characters to describe the type of service.

E.g. SRV_MAIL, SRV_FTP, SRV_SEEBRG

Adapter Objects

Adapter Meta Data

AM_<meaningful name>

Communication Channel

CC_<meaningful name>_<sender/receiver>

            E.g. CC_MAIL_SENDER

Integration Objects

Integration Process

IP_<meaningful name> (Keep to 10 or less characters – ALL CAPS)

            Store these in namespace http://ERPGenie.COM/xi/<SCENARIO>

Actions

<meaningful name>

Use Send_ or Receive_ to denote the sending or receiving of messages

Store these in namespace http://ERPGenie.COM/xi/<SCENARIO>/<SID> where <SID> is system where the action is to be performed.

Integration Scenarios

IS_<meaningful name> (Keep to 10 or less characters – ALL CAPS)

            Store these in namespace http://ERPGenie.COM/xi/<SCENARIO>

Contact Us | Polls | Add URL | Contribute | About | Privacy | Terms | Feedback | Help!

Message Board | Discussion Forum | BLOG | Consultants: Post your resume | Companies: Advertise on ERPGenie.COM | Post Job