Need Seeburger Mapping name for DESADV .

[Former Member]

Hi All,

I want the Seeburger mapping name for DESADV .

The format of the file is ANSI file.

Also i want the folder name or standard number for DESADV ??

I mean like for Orders the folder name will be " ANSIX12_V3020_850 "

Kindly let me know asap.

Thank You.

Regards

Seema.

[Former Member · Accepted solution]

Hi,

Seeburger Mapping name for DESADV will be

<b>(See_ )_ANSIX12_850_V4010</b> as per my knowledge.

Are u sure about the folder name for Orders that u have given.?

Regards,

Anoop

[Former Member · Accepted solution]

Hi Anoop,

The mapping name which you gave is for OREDERS (Number : 850).

I want the standing mapping name for DESADV (Number : ???).

Thanks.

-seema.

[former_member181962 · Accepted solution]

the DESADV EDI signal is 856.

[Former Member · Accepted solution]

Thanks Ravi,

will you please tell me the Seeburger std mapping names for EDIFACT(EANCOM2002) file for the below msg types.

DESADV

ORDERS

ORDRSP

INVOICE

Thank You.

-Seema.

[former_member181962 · Accepted solution]

Hi Reddy,

Ideally the this is how it is.

DESADV-> Shipping Notification->We tell the customer that we are about to send some goods-> so it is 856 signal (Outbound from our system).

ORDERS->Order->Customer sends the orders as 850 signal and we convert that signal into ORDERS idoc and this idoc will create a sales order in our system.

ORDRSP->Order Response, we can map this signal to 855 with is the Order acknowledgement i.e the document that we send to the customer saying that their order is either accepted or rejected.

Invoice-> we send an invoice idoc to the customer, which will be converted into 810 document in our XI.

learn more about other EDI transaction sets here:

http://www.erpgenie.com/sapedi/index.htm

Regards,

Ravi Kanth Talagana

[Former Member]

Hi,

These are the few naming conventions that will be followed while doing mapping in SEEBURGER BIC mapping designer.Let me know if they help u in any way..

ADOPTED NAMING CONVENTIONS

1 - For Application Rules:

DOCUMENT_APLLICATION_DIRECTION_DATA (FILE EXTENSION FOR REFERENCE)

Length for each:

Document = 3 Samples of: PUR, POC, POA, ASN, TXT

Application = 4 Samples of: RECL, SOMS, HRMS, CORP, COMS, CONT

Direction = 1 Samples of: I or O

Data = 3 Samples of: DAT, XML, RPT

NOTE: Since spaces are not allowed in the names, ‘S’ will be used as filler .

Sample Application Naming:

For 824 for Banking doc – TXT_CORP_I_RPT

2 - For Project Rules:

We decided that we would group these by related documents. Ex. All PO’s would be together.

Following are the Project definitions:

ORDERS (PURCHASING) = 850, 880

BANKING = 820, 824 (Related to the banking 820 only)

TRANSPORTATION = 404, 858, 856, 940, 945, 990, ..

INVOICING = 810, 857

TEXT = 824, 864, 870

INVENTORY = 852, 830, 846,..

3 – General Rules:

1- IF mapping is the same with HRMS & COMS

THEN Use CONT for Application

ELSE Use HRMS or COMS (which ever is appropriate)

2- IF document is the same for the entire corporation

THEN Use CORP as the Application

3- IF Generic

THEN No Suffix is required

ELSE Trading Partner Specific maps add the suffix

For Trading Partner specific rules, add the Name extension to the end of the rule

Thanks .