EDI in purchasing

Hello SAP professionals,
I encounter an error message " Sender partner number in condition record is default" when the vendor releases for a MM SA are releases released thro EDI. It looks like the releases are released thro EDI. but I could not see any Idoc for this transaction.
I have checked partner profiles by calling up WE20 and the message control for outbound parameters look all right. NACE, the output type for partner function is set up all right. I could not figure out what I am missing.
Could any one of you please give me some suggestions on this?.
Thanks and regards

Hi Jurgen,
Please see the diagonosis of this error message
EDI: Sender partner number in control record is default
Message no. EA608
Diagnosis
An error was identified in the control record while adding an IDoc. No value has been entered for the sender partner number, which is not permitted.
Procedure
Please inform your system administrator
Thanks

Similar Messages

EDI from Purchase Order to Sales Order

Hi all,
I've customized the EDI system: at purchase order creation the system automatically creates a sales order(inside the same system). Now i'm facing the following situation : since PO data is very different from SO data (eg. terms of payment), i'm getting errors when i integrate the sales order idoc. Is there a way that i can "map" the "transalation" of the PO to SO data. How can i do this? Best regards,
PCastro

Pedro, when you create the SO , what are the steps before creating the Idoc, is it automated, if not you can maybe write some ABAP code and change the data before the Idoc is created.
I cannot get the full picture of what you are doing but if the Idoc creation in not automatic you can always change the values in some ABAP code.
If it is automatic, see if there are any user exits.
Regards

Idoc using EDI for purchase order

hi all,
could someone explain me all the steps required in generating purchase order idoc using EDI butnot using ALE.
i want all the steps to be in detail.
thanks in advance
suma sailaja pvn

EDI is described as the interchange of structured data according to agreed message standards between computer systems, by electronic means. Structured data equates to a simple and direct method of presenting the data content of a document. The method of ensuring the correct interpretation of the information by the computer system is defined by the EDI standard."
EDI is a technique used to communicate business transactions between computer systems of different companies and organizations. Note that sometimes the EDI mechanism deployed at a company is often used to interface to other systems within the same organization."
The difference between ALE and EDI process flows occurs at the communication level. The EDI process transmits IDocs to an EDI subsystem using flat file format. The ALE process transmits IDocs to an SAP system via memory, using asynchronous communication.
Check the following links
How Can I transfer invoice details to customer through IDOC in EDI
Re: IDOC Types and their equivalent messages in EDIFACT and ANSI X12
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.henrikfrank.dk/abapexamples/IDOC/IDOC.htm
http://help.sap.com/printdocu/core/Print46c/en/Data/Index_en.htm
http://help.sap.com/saphelp_47x200/helpdata/en/0b/2a6095507d11d18ee90000e8366fc2/frameset.htm
Reward Points if useful.

Edi for purchase order

hi,
can any one say me the step to send a Purchase order through an EDI

EDI is described as the interchange of structured data according to agreed message standards between computer systems, by electronic means. Structured data equates to a simple and direct method of presenting the data content of a document. The method of ensuring the correct interpretation of the information by the computer system is defined by the EDI standard."
EDI is a technique used to communicate business transactions between computer systems of different companies and organizations. Note that sometimes the EDI mechanism deployed at a company is often used to interface to other systems within the same organization."
The difference between ALE and EDI process flows occurs at the communication level. The EDI process transmits IDocs to an EDI subsystem using flat file format. The ALE process transmits IDocs to an SAP system via memory, using asynchronous communication.
Check the following links
How Can I transfer invoice details to customer through IDOC in EDI
Re: IDOC Types and their equivalent messages in EDIFACT and ANSI X12
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.henrikfrank.dk/abapexamples/IDOC/IDOC.htm
http://help.sap.com/printdocu/core/Print46c/en/Data/Index_en.htm
http://help.sap.com/saphelp_47x200/helpdata/en/0b/2a6095507d11d18ee90000e8366fc2/frameset.htm
Reward Points if useful.

EDI 860 - Purchase Order Change Request in SRM

Hello All,
I'm working on a problem involving the generation of the EDI 860 when a Purchase Order in changed in SRM. If anyone is familiar with this functionality please contact me and I will have specific questions.
Thank you,
JR

Hi,
I wonder why would you want to do that. Any change to the PO is internal to your organisation till such a PO is ordered(approved). Once ordered you can anyways send the output to you vendor which would inform him of the changes.
Regards
Azad

EDI Outbound Purchase Order Please check

Hi,
My requirment is i have one outbound IDOC, i have to change some data inthe segment E1EDKA1 form some coustam tables
The Basic type is Orders05, i should do some changes in the segment E1EDKA1 based on E1EDKA1-PARVW in the exit EXIT_SAPLEINM_011,
i have written the code in the exit EXIT_SAPLEINM_011, Can any body pls check my code
TYPES:BEGIN OF ty_ztsd_ilnpurorg,
       bbbnr TYPE ztsd_ilnpurorg-bbbnr,
       bbsnr TYPE ztsd_ilnpurorg-bbsnr,
       bubkz TYPE ztsd_ilnpurorg-bubkz,
      END OF ty_ztsd_ilnpurorg,
      BEGIN OF ty_ztsd_ilnplant,
       bbbnr TYPE ztsd_ilnplant-bbbnr,
       bbsnr TYPE ztsd_ilnplant-bbsnr,
       bubkz TYPE ztsd_ilnplant-bubkz,
      END OF ty_ztsd_ilnplant,
      BEGIN OF ty_kna1,
       bbbnr TYPE kna1-bbbnr,
       bbsnr TYPE kna1-bbsnr,
       bubkz TYPE kna1-bubkz,
      END OF ty_kna1.
*&                    WORK AREA
DATA: lw_ztsd_ilnpurorg TYPE ty_ztsd_ilnpurorg,
      lw_ztsd_ilnplant TYPE ty_ztsd_ilnplant,
      lw_kna1           TYPE ty_kna1,
      lw_edidd          TYPE edidd,
      lw_e1edka1        TYPE e1edka1.
*&                    VARIABLES
DATA:l_bbbnr      TYPE ztsd_ilnpurorg-bbbnr,
     l_bbsnr      TYPE ztsd_ilnpurorg-bbsnr,
     l_bubkz      TYPE ztsd_ilnpurorg-bubkz,
     l_ilnnr      TYPE e1edka1-ilnnr,
     l_kna1_bbbnr TYPE kna1-bbbnr,
     l_kna1_bbsnr TYPE kna1-bbsnr,
     l_kna1_bubkz TYPE kna1-bubkz,
     l_kna1_partn TYPE e1edka1-partn,
     l_e1edka1_we TYPE e1edka1-ilnnr.
*&                    CONSTANTS
CONSTANTS:lc_orders05(8) TYPE c VALUE 'ORDERS05',
          lc_eledka1(7) TYPE c VALUE 'E1EDKA1'.
Clearing the workarea
CLEAR:lw_ztsd_ilnpurorg,
      lw_ztsd_ilnplant,
      lw_kna1,
      lw_edidd,
      lw_edidd_1,
      lw_e1edka1,
      lw_e1edp19.
*Checking for the Idoc type ORGERS05
IF control_record_out-idoctp = lc_orders05.
*Reading the EDIDD table for the segment E1EDKA1
READ TABLE dint_edidd INTO lw_edidd WITH KEY segnam = lc_eledka1.
IF sy-subrc = 0.
    MOVE lw_edidd-sdata TO lw_e1edka1.
ENDIF.
*checking the segment E1EDKA1-PARVW
CASE lw_e1edka1-parvw.
    WHEN 'AG'.
*Selecting the data required for conversion of E1EDKA1-ILNNR to Campina ILN number
      SELECT SINGLE bbbnr bbsnr bubkz
             INTO lw_ztsd_ilnpurorg
             FROM ztsd_ilnpurorg
             WHERE ekorg = lw_e1edka1-paorg.
      IF sy-subrc = 0.
        l_bbbnr = lw_ztsd_ilnpurorg-bbbnr.
        l_bbsnr = lw_ztsd_ilnpurorg-bbsnr.
        l_bubkz = lw_ztsd_ilnpurorg-bubkz.
      ENDIF.
      CONCATENATE l_bbbnr l_bbsnr l_bubkz INTO l_ilnnr.
*Conversion of E1EDKA1-ILNNR to Campina ILN number
      CLEAR dint_edidd.
      CLEAR lw_e1edka1.
      lw_e1edka1-ilnnr = l_ilnnr.
      MOVE lw_e1edka1 TO lw_edidd-sdata.
      MODIFY dint_edidd FROM lw_edidd TRANSPORTING sdata.
Clearing the workarea
CLEAR:lw_ztsd_ilnpurorg,
      lw_edidd,
      lw_e1edka1,
      l_bbbnr,
      l_bbsnr,
      l_bubkz,
      l_ilnnr.
    WHEN 'SP'.
*Selecting the data required for conversion of E1EDKA1-ILNNR to Plant ILN number
      SELECT SINGLE bbbnr bbsnr bubkz
             INTO lw_ztsd_ilnplant
             FROM ztsd_ilnplant
             WHERE werks = lw_e1edka1-lifnr.
      IF sy-subrc = 0.
        l_bbbnr = lw_ztsd_ilnplant-bbbnr.
        l_bbsnr = lw_ztsd_ilnplant-bbsnr.
        l_bubkz = lw_ztsd_ilnplant-bubkz.
      ENDIF.
      CONCATENATE l_bbbnr l_bbsnr l_bubkz INTO l_ilnnr.
*Conversion of E1EDKA1-ILNNR to Plant ILN number
      CLEAR dint_edidd.
      CLEAR lw_e1edka1.
      lw_e1edka1-ilnnr = l_ilnnr.
      MOVE lw_e1edka1 TO lw_edidd-sdata.
      MODIFY dint_edidd FROM lw_edidd. "TRANSPORTING sdata.
Clearing the workarea
CLEAR:lw_ztsd_ilnplant,
      lw_edidd,
      lw_e1edka1,
      l_bbbnr,
      l_bbsnr,
      l_bubkz,
      l_ilnnr.
    WHEN 'WE'.
*Selecting the data required for conversion of E1EDKA1-PARTN to ILN number from customer master KNA1
      SELECT SINGLE bbbnr bbsnr bubkz
             INTO lw_kna1
             FROM kna1
             WHERE kunnr = lw_e1edka1-partn.
      IF sy-subrc = 0.
        l_kna1_bbbnr = lw_kna1-bbbnr.
        l_kna1_bbsnr = lw_kna1-bbsnr.
        l_kna1_bubkz = lw_kna1-bubkz.
      ENDIF.
      CONCATENATE l_kna1_bbbnr l_kna1_bbsnr l_kna1_bubkz INTO l_kna1_partn.
      FREE:lw_ztsd_ilnplant.
*Selecting the data required for conversion of E1EDKA1-LIFNR to Plant ILN number
      SELECT SINGLE bbbnr bbsnr bubkz
             INTO lw_ztsd_ilnplant
             FROM ztsd_ilnplant
             WHERE werks = lw_e1edka1-lifnr.
      IF sy-subrc = 0.
        l_bbbnr = lw_ztsd_ilnplant-bbbnr.
        l_bbsnr = lw_ztsd_ilnplant-bbsnr.
        l_bubkz = lw_ztsd_ilnplant-bubkz.
      ENDIF.
      CONCATENATE l_bbbnr l_bbsnr l_bubkz INTO l_ilnnr.
*Checking PARTN and LIFNR for data
      IF l_kna1_partn IS NOT INITIAL.
        MOVE l_kna1_partn TO l_e1edka1_we.
      ELSE.
        MOVE l_ilnnr TO l_e1edka1_we.
      ENDIF.
*Conversion of E1EDKA1-PARTN to ILN number from customer master KNA1
             E1EDKA1-LIFNR to Plant ILN number
*Check and Convert PARTN and LIFNR and copy the field contents to ILNNR
      CLEAR dint_edidd.
      CLEAR lw_e1edka1.
      lw_e1edka1-partn = l_kna1_partn.
      lw_e1edka1-lifnr = l_ilnnr.
      lw_e1edka1-ilnnr = l_e1edka1_we.
      MOVE lw_e1edka1 TO lw_edidd-sdata.
      MODIFY dint_edidd FROM lw_edidd. "TRANSPORTING sdata.
*Free the work area and local variables
      FREE:lw_e1edka1,
           lw_edidd,
           l_bbbnr,
           l_bbsnr,
           l_bubkz,
           l_ilnnr.
ENDCASE.
It would be very help full if any body can quickely check the code and reply back,
Thanks in advance,
sai.

Dear
Please check setting in IMG SAP Supl.Rel.Management>SRM Server>Technical Basic Setting>Define Back end system for Product category.
Thanks & Regards
Rajendran

EDI 850: one vendor, multiple purchasing orgs

We have sussessfully implemented EDI 850 (purchase order) interface by using PO output, IDoc ORDERS05 and ABAP-PI port with a custom function module, which writes the IDoc data into a file and sends it to a third-party software (Gentran).
Now the problem is that we have 2 purchasing organizations (EKORG) and for each organization we need to create a separate file and send it to a different FTP server. Unfortunately, EKORG is not included anywhere in the IDoc control record (EDI partner profile is set up by vendor), only in the IDoc segments.
Has anyone had the same issue and what would you recommend?

Hi Jelena,
Welcome to SDN.
Are you using process code ME10 (FM IDOC_OUTPUT_ORDERS)?
If you are then there is user exits EXIT_SAPLEINM_001 that can be used to add additional information to IDoc control record.
For example you can use EDIDC-MESCOD and/or EDIDC-MESFCT to populate the mapping for your purchasing organization (EKORG).
You can code something like this inside user exits.
IF EKKO-EKORG = '0001'
CONTROL_RECORD_OUT-MESCOD = '1'.
ELSEIF EKKO-EKORG = '0002'.
CONTROL_RECORD_OUT-MESCOD = '2'.
ELSE.
ENDIF.
then you can use CONTROL_RECORD_OUT-MESCOD to distinguish/map purchase organization into EDI850 in the middleware system (Gentran).
Hope this will help.
Regards,
Ferry Lianto

Automatic PO creation through EDI

Hi experts,
Please clarify me on the setup of creating PO's thru EDI in Purchasing automatically once PR is created in the system.
My client is more or less a trading company. They buy from vendor & sell to their customer, like third party order process.
So they create Sales Order & then PReq is created through ME57 & then they create PO through ME59.
They want to create PO's automatically thru EDI as this can speed up the process so as the vendor is also looking for creating SO in their BaaN system automatically.
I have configured the EDI setup for creating PO manually, meaning when I create manual PO the idoc xml file is ready for transfer.
But I am looking for the steps so that once they create the PReq, EDI should automatically create PO in SAP & the idoc should be ready for transfer.
Please suggest if this can be done thru any BAPI or BDC programs.
Thanks in advance !
Priyadarshini

Hi Krishna,
This is for automatically creating normal PO thru PReq. Since I have setup the EDI configs for creating PO thru manual process thru Me21N then idoc gets generated.
But my client is looking for the idocs to be generated automatically once the PReq are created thru Me57.
is there a way?
Rgds,
Pri

B2B Error while generating 850 EDI Document

Hi All,
We are facing the following error in B2B while generating an EDI 850 outbound document.
To give a brief background of our process:
We are using a BPEL process to pick a fixed length file from FTP adapter and then transform it and provide it to B2B for converting it into an EDI 850 Purchase Order. The BPEL part of the Process is working fine and it is successfully transforming the fixed length file into intermediate XML that it gives to B2B engine.
In B2B, the ECS file that we use has been generated from an XSD and we upload the corresponding ECS and XSD in B2B during configuration.
But we get the following error when B2B converts it into EDI 850 format.
Error Brief :
5084: XEngine error - Invalid data.
I am also giving around 100 lines from the b2b log before this error occurred.
2006.10.30 at 01:50:14:416: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter AcknowledgementType = 997
2006.10.30 at 01:50:14:416: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter GroupSenderID = 19508030411I
2006.10.30 at 01:50:14:416: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter InterchangeECSFileBlob
2006.10.30 at 01:50:14:416: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter InterchangeAuthorizationInfoQual = 00
2006.10.30 at 01:50:14:416: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter GroupID = PO
2006.10.30 at 01:50:14:416: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter TagDelimiter = null
2006.10.30 at 01:50:14:417: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter TransactionECSFileKey = 1BA24E3F6DB690CAE0430A0B3E7290CA-274-1-42
2006.10.30 at 01:50:14:417: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter InterchangeSecurityInfoQual = 00
2006.10.30 at 01:50:14:417: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter GroupECSFileBlob
2006.10.30 at 01:50:14:417: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter TPName = CANON
2006.10.30 at 01:50:14:417: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter TransactionImplementationReference = null
2006.10.30 at 01:50:14:417: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter ReplacementChar = null
2006.10.30 at 01:50:14:417: Thread-11: Repository - (DEBUG) CatalogDriver manager == oracle.tip.model.metadata.CatalogMetaManager@9f90cf3
2006.10.30 at 01:50:14:417: Thread-11: Repository - (DEBUG) CatalogMetaManager getDriverjava.lang.InheritableThreadLocal@72418cf0 oracle.tip.repos.core.driver.CatalogDriver@121ccf4
2006.10.30 at 01:50:14:418: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Enter
2006.10.30 at 01:50:14:419: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl fullOutboundBatching = false
2006.10.30 at 01:50:14:419: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl validateEnvelope = true
2006.10.30 at 01:50:14:419: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Leave
2006.10.30 at 01:50:14:419: Thread-11: Repository - (DEBUG) LargeStringImpl.getString() - object OID - 20D326898FA9D054E0430A0B3E72D054-11-1-1
2006.10.30 at 01:50:14:421: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup Enter
2006.10.30 at 01:50:14:421: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = ec_DataNodeName, val = [Interchange]
2006.10.30 at 01:50:14:421: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
2006.10.30 at 01:50:14:422: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
2006.10.30 at 01:50:14:422: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
2006.10.30 at 01:50:14:422: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@34c90cf5
2006.10.30 at 01:50:14:422: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = InterchangeSenderQual
2006.10.30 at 01:50:14:422: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 01
2006.10.30 at 01:50:14:422: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = InterchangeSenderID
2006.10.30 at 01:50:14:422: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 195080304
2006.10.30 at 01:50:14:422: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = InterchangeReceiverQual
2006.10.30 at 01:50:14:422: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 01
2006.10.30 at 01:50:14:423: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = InterchangeReceiverID
2006.10.30 at 01:50:14:423: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 0415306925
2006.10.30 at 01:50:14:423: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = InterchangeControlVersion
2006.10.30 at 01:50:14:423: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 00401
2006.10.30 at 01:50:14:423: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup Enter
2006.10.30 at 01:50:14:423: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = ec_DataNodeName, val = [Group]
2006.10.30 at 01:50:14:423: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
2006.10.30 at 01:50:14:423: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
2006.10.30 at 01:50:14:423: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
2006.10.30 at 01:50:14:424: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@2c760cf5
2006.10.30 at 01:50:14:424: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = GroupID
2006.10.30 at 01:50:14:424: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = PO
2006.10.30 at 01:50:14:424: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = GroupSenderID
2006.10.30 at 01:50:14:424: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 19508030411I
2006.10.30 at 01:50:14:424: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = GroupReceiverID
2006.10.30 at 01:50:14:424: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 0415306925
2006.10.30 at 01:50:14:424: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = GroupVersionNumber
2006.10.30 at 01:50:14:424: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 004010
2006.10.30 at 01:50:14:425: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup Enter
2006.10.30 at 01:50:14:425: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = ec_DataNodeName, val = [Transaction]
2006.10.30 at 01:50:14:425: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
2006.10.30 at 01:50:14:425: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
2006.10.30 at 01:50:14:425: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
2006.10.30 at 01:50:14:425: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@25070cf5
2006.10.30 at 01:50:14:425: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = TransactionID
2006.10.30 at 01:50:14:425: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 850
2006.10.30 at 01:50:14:427: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = SegmentDelimiter
2006.10.30 at 01:50:14:427: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 0x0A
2006.10.30 at 01:50:14:427: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = ElementDelimiter
2006.10.30 at 01:50:14:427: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 0x7D
2006.10.30 at 01:50:14:427: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = SubelementDelimiter
2006.10.30 at 01:50:14:427: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 0x3E
2006.10.30 at 01:50:14:427: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = RepeatingSeparator
2006.10.30 at 01:50:14:427: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = null
2006.10.30 at 01:50:14:428: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = ReplacementChar
2006.10.30 at 01:50:14:428: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = null
2006.10.30 at 01:50:14:428: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:reset Enter
2006.10.30 at 01:50:14:428: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:reset Leave
2006.10.30 at 01:50:14:428: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = TPName
2006.10.30 at 01:50:14:428: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = CANON
2006.10.30 at 01:50:14:429: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Enter
2006.10.30 at 01:50:14:429: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Leave
2006.10.30 at 01:50:14:429: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument XML = 1
2006.10.30 at 01:50:14:429: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument no result from XDataToNative
2006.10.30 at 01:50:14:442: Thread-11: B2B - (DEBUG) iAudit report :
Error Brief :
5084: XEngine error - Invalid data.
iAudit Report :
<?xml version="1.0" encoding="UTF-16"?><AnalyzerResults Guid="{06B942E5-E267-DB11-9E73-006163130000}" InterchangeReceived="1" InterchangeProcessed="1" InterchangeAccepted="0"> <ExecutionDate>Monday, October 30, 2006</ExecutionDate> <ExecutionTime>01:50:14 AM (EST)</ExecutionTime> <AnalyzerReturn>Failed</AnalyzerReturn> <NumberOfErrors>1</NumberOfErrors> <ErrorByCategory> <Category Name="Rejecting"> <Severity Name="Normal">1</Severity> </Category> </ErrorByCategory> <Status>Finished</Status> <DataFile> <FilePath/> <FileName/> <LastModified/> <FileSize/> <DataURL>file://</DataURL> </DataFile> <Interchange Guid="{424043E5-E267-DB11-9E73-006163130000}" InterchangeAckCode="R" FunctionalGroupReceived="1" FunctionalGroupProcessed="1" FunctionalGroupAccepted="0" RError="0" NError="0" OtherWI="0"> <DataXPointer> <StartPos>0</StartPos> <Size>1337</Size> </DataXPointer> <NodeInfo> <Links> <Link Name="InterchangeSenderQual">01</Link> <Link Name="InterchangeSenderID">195080304</Link> <Link Name="InterchangeReceiverQual">01</Link> <Link Name="InterchangeReceiverID">0415306925</Link> <Link Name="InterchangeControlVersion">00401</Link> </Links> <Properties> <Property Name="Standard">X12</Property> <Property Name="SegmentDelimiter">0xa</Property> <Property Name="ElementDelimiter">0x7d</Property> <Property Name="SubelementDelimiter">0x3e</Property> <Property Name="RepeatingSeparator"/> <Property Name="ReplacementChar">0x20</Property> </Properties> </NodeInfo> <FunctionalGroup Guid="{F28543E5-E267-DB11-9E73-006163130000}" FunctionalGroupAckCode="R" TransactionSetsIncluded="0" TransactionSetsReceived="1" TransactionSetsProcessed="1" TransactionSetsAccepted="0" RError="0" NError="0" OtherWI="0"> <DataXPointer> <StartPos>0</StartPos> <Size>1337</Size> </DataXPointer> <NodeInfo> <Links> <Link Name="GroupSenderID">19508030411I</Link> <Link Name="GroupReceiverID">0415306925</Link> <Link Name="GroupVersionNumber">004010</Link> </Links> <Properties> <Property Name="GroupID">PO</Property> </Properties> </NodeInfo> <Transaction Guid="{33303938-3738-3533-3630-353932353933}" TransactionAckCode="R" RError="1" NError="0" OtherWI="0"> <DataXPointer> <StartPos>0</StartPos> <Size>1337</Size> </DataXPointer> <NodeInfo> <Links> <Link Name="TransactionID">850</Link> </Links> <Properties/> </NodeInfo> <TransactionErrors> <Error ErrorCode="{F35AFE03-C479-4F96-B4F1-2EF36DABC5FE}" Severity="Normal" Category="Rejecting" Index="1" ID="50840000"> <ErrorBrief>5084: XEngine error - Invalid data.</ErrorBrief> <ErrorMsg>Invalid data.</ErrorMsg> <ErrorObjectInfo> <Parameter Name="ErrorLevel">0</Parameter> <Parameter Name="Name">XData2Native</Parameter> <Parameter Name="_ec_dn_guid_">{33303938-3738-3533-3630-353932353933}</Parameter> <Parameter Name="_ec_index">0</Parameter> <Parameter Name="ec_error_scope">Transaction</Parameter> </ErrorObjectInfo> <ErrorDataInfo> <Part1/> <ErrData/> <Part3/> <DataXPointer> <StartPos>0</StartPos> <Size>0</Size> </DataXPointer> </ErrorDataInfo> </Error> </TransactionErrors> </Transaction> </FunctionalGroup> </Interchange></AnalyzerResults>
2006.10.30 at 01:50:14:443: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sErrorGuid = {F35AFE03-C479-4F96-B4F1-2EF36DABC5FE}
2006.10.30 at 01:50:14:443: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sDescription = Invalid data.
2006.10.30 at 01:50:14:443: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sBrDescription = 5084: XEngine error - Invalid data.
2006.10.30 at 01:50:14:443: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = ErrorLevel sParameterValue = 0
2006.10.30 at 01:50:14:443: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = Name sParameterValue = XData2Native
2006.10.30 at 01:50:14:443: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = ecdn_guid_ sParameterValue = {33303938-3738-3533-3630-353932353933}
2006.10.30 at 01:50:14:443: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = ecindex sParameterValue = 0
2006.10.30 at 01:50:14:444: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = ec_error_scope sParameterValue = Transaction
2006.10.30 at 01:50:14:444: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument added Hash Key = {33303938-3738-3533-3630-353932353933}
2006.10.30 at 01:50:14:444: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument batch Position = 0
2006.10.30 at 01:50:14:444: Thread-11: B2B - (ERROR) Error -: AIP-51505: General Validation Error
     at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:1668)
     at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1132)
     at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:710)
     at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:821)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:532)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java(Compiled Code))
     at java.lang.Thread.run(Thread.java:568)
If anybody has faced a similar issue, then please post on how to overcome this error.
Thanks In Advance,
Dibya

Hi,
I am facing a similar problem.
I am trying to transfer a xml in 850 format with internal properties of Interchange,Group and Transaction from BPEL to B2B.My BPEL setup consist of :
A partnerlink which read xml in 850 format using file adapter.
A receive Activity which receive the data.
I have created a partnerlink which use AQ Adapter to enqueue data in IP_OUT_QUEUE.
A invoke Activity invokes this partnerlink.
Then I have assigned the read data in Receive to input variable of Invoke activity.
I have used another Assign Activity to populate the Header; and passed this header in Invoke Activity.
In B2B I have created two trading partner one remote and one host, defined a business action and defined the Communication capability for them. I am using FTP1.0 . I defined a agreement and deployed the configuration in b2b server.
The ecs and xsd I am using is the one provided with Purchase order tutorial, it contains only ST-SE,I have also tried with envelope segments for 4010-namely
ISA-->GS-GE-->IEA.When I am turning off validation and translation its throwing the input XML as output in the .dat file. If I turn on Translation I am getting unrecognized data last known segment is GSA.In this case the input XML had internal properties of Interchange and Group.If I remove the transaction part from ST-SE the dat file is generated in native dat format but with ISA -GS-GE -IEA but no transaction portion.
As a work around I tried seperate group ecs,interchange ecs and transaction ecs and tried to pass a 850 xml with only transaction fields.
I have tried with no ecs file at all and in that case the dat file is also generated.So does this mean that B2B have seeded ecs file which it use as default if I dont use any ecs file?
It seems from the post you have successfully completed this part can u send me :
1>The 850 ecs and xsd file you used.
2>If you have used any group ecs and interchange ecs.
3>The input you are sending in BPEL.
4>The BPEL process and B2B export xml you are using in zipped format.
My mail ID: [email protected]
phone:09831964607
I tried out different ways suggested in the post but nothing seem to be working for me,I am still getting the invalid data error and if it is creating the dat file only envelope segments are created.
If you send me the working example I can work on it as baseline, this will be of great help in my work.

Problem in using output type for purchase order

Hi experts,
I am using output type for first time so may be i have done wrong configuration for po output type.The steps i have done are :-
1) Going to tcode NACE->Selected the row u201CEF Purchase Orderu201D and clicked on u201CProcedures".
2) In procedures there are 2 procedures for the application EF (Purchase Order). To proceed further, we would need to find out the procedure that is currently active.Gone to transaction SPRO. In this, navigate as Materials management -> Purchasing ->Messages -> Output control -> Message Determination Schemas ->Define Message Schema for Purchase Order
3) Clicking on u201CAssign Schema to Purchase Orderu201D. So, the procedure RMBEF1 is active for EF (Purchase Order) .
4) Go back to transaction NACE. Select u2018EFu2019 and click on u201COutput typesu201D.
5) Let us use the output type u201CNEU name purchase orderu201D for this purpose. Double-click on NEU.
6) Ensured that the checkboxes u201CAccess to conditionsu201D and u201Cmultiple issuingu201D are checked and the access sequence is 0001(DocType/PurchOrg/Vendor).Only 0001 and 0002 is available in f4 help for this.
7) Now clicked on u201CProcessing Routinesu201D on the left hand side. Ensured that there is an entry for Medium u2018Au2019 (Distribution ALE).
8) After that going back to the main screen of NACE. Select EF (Purchase Order) and clicked on u201CCondition Recordsu201D.
Select NEU and clicked on u201CCondition recordsu201D. The pop-up box appears that gives three radio button option :-
1) Purchasing output determination :purchasing org / vendor for EDI
2) Purchasing output determination :doc. type / purchasing org /vendor
3) Purchasing output determination :document type
but it is not having option only for purchasing organisation through which we can send idoc for changes or creation of PO in that particular pur.org now if i choose 2) i have to give doc type and purchasing org both bcoz they are mandatory fields and value for vendor.
9) Also i have done the necessary ALE configuration (not covered in this document). In the partner profiles, use the message type u201CORDERSu201D and the IDOC type u201CORDERS05u201D.In the tab u201CMessage Controlu201D, used the process codes u201CME10u201D and u201CME11u201D for u201CPO Createu201D and u201CPO Changeu201D respectively.
but the idoc is not generated many times when po is changed and when once it is generated it is giving error
Please suggest solution.
Thanks in advance
nehavt

In me22n in messages tab after looking into processing log it is giving->No recipient found for message type ORDCHG in the
ALE model ,next time giving error as no idoc items belonging to purchasing document found,when i changed message type to ORDCHG the status is green in messages tab it is giving-> error occured while idoc xyz is sent and in WE02 status is red 02
error passing data to port(could not find code page for receiving system)

Automate PO creation through EDI

Hi experts,
Please clarify me on the setup of creating PO's thru EDI in Purchasing automatically once PR is created in the system.
My client is more or less a trading company. They buy from vendor & sell to their customer, like third party order process.
So they create Sales Order & then PReq is created through ME57 & then they create PO through ME59.
They want to create PO's automatically thru EDI as this can speed up the process so as the vendor is also looking for creating SO in their BaaN system automatically.
I have configured the EDI setup for creating PO manually, meaning when I create manual PO the idoc xml file is ready for transfer.
But I am looking for the steps so that once they create the PReq, EDI should automatically create PO in SAP & the idoc should be ready for transfer.
Please suggest if this can be done thru any BAPI or BDC programs.
Thanks in advance !
Pri

In the program after the pur. req. created, find user exit and check the BAPI_PO_CREATE1. Configure the ALE setting for PO IDoc creation or XML creation..
Thanks,
krishna

Changing a Purchase Order with "BAPI_PO_CHANGE"

Hi Experts,
I am trying to change the Confirmation data for an existing PO using the BAPI "BAPI_PO_CHANGE".
I am filling the PO Number in the "PURCHASEORDER" Import parameter.
I am also filling the "CONF_TYPE", "DELIV_DATE" and "QUANTITY" fields in the "POCONFIRMATION" Table parameter which is specifically the data i need to add to the existing PO under the "Confirmations" tab of the PO.
I am getting all the input data for the BAPI from a file on the presentation server. The file has details of Material Number, Purchase Order Number, Ship to Address, Delivery Date and Quantity.
But i am not able to change any data in the Purchase Order when i test the BAPI. I am getting the following messages in the "RETURN" Tables parameter:
T ID                   NUM MESSAGE
W ME                   667 Max. line number reached (Please always first enter line number manually)
E BAPI                 003 Instance 45317399 of object type PurchaseOrder could not be changed
W ME                   178 Batch SURE not maintained for material 10013537 (please check your input)
E 06                   218 Net price must be greater than 0
I am not sure if i am missing to fill any parameter here.
Kindly help me in resolving this issue.
Thanks in advance.
Regards,
Keerthi

Hello to all,
that is just for documentation. SAP answerd the problem in OSS-304243 but this message is not accessable if you don't have powerful OSS-Users.
This SAP-note might be interesting: 197958
OSS-Message 652796 8.8.2011
BAPI_PO_CHANGE
We can not process confirmations by using the parameter poconfirmation.
The Baps reports always S 06 022 - no data changed.
In the SDN there are some hints telling that the BAPI_PO_CHANGE does notsupport processing of confirmations. More detailled infos should be in
the OSS-Message 0000304243 but this message is not accessable for us.
Can you confirm that the BAPI_PO_CHANGE does not support adding
confirmations? We debugged the BAPI and there is no code for updating
confirmations found.
Best regards
Bernhard Lascy
09.08.2011 - 10:43:07 CET - Antwort von SAP
Dear Bernhard,
I regret to inform you that the functionality you request is not
implemented in the R/3 standard system.
Unfortunately it is not possible to change/load confirmations with the
function module BAPI_PO_CREATE/BAPI_PO_CHANGE. Table POCONFIRMATION in
BAPI interface is relevant for Display/List Vendor Confirmation in BAPI,not for update/insert Vendor confirmation in PO.
Furthermore, we recommends that you use Idocs for automatically
entering confirmations. The Message type to use is ORDRSP.
You may read more about this topic in the online documentation.
Please see also following attached note for your reference.
456127 FAQ: Electronic Data Interchange (EDI) in purchasing
Best regards,
Pavel Olysar
Support Consultant
Global Support - Logistics

BAPI to add Purchase Order Confirmation?

Hi,
I have to add PO Confirmations and I found the BAPI 'BAPI_PO_CHANGE' that have an "tables" parameter for my requeriment. But I created a test program and I checked that it doesn't work for that purpouse (and I'm not the 1st one who find that problem: [Re: BAPI_PO_CHANGE is not updating Confirmation Category and Date cate Category; ). I checked the code and the BAPI really don't do anything with POCONFIRMATION data except read it....
Have you an alternative for this??

Hello to all,
that is just for documentation. SAP answerd the problem in OSS-304243 but this message is not accessable if you don't have powerful OSS-Users.
This SAP-note might be interesting: 197958
OSS-Message 652796 8.8.2011
BAPI_PO_CHANGE
We can not process confirmations by using the parameter poconfirmation.
The Baps reports always S 06 022 - no data changed.
In the SDN there are some hints telling that the BAPI_PO_CHANGE does notsupport processing of confirmations. More detailled infos should be in
the OSS-Message 0000304243 but this message is not accessable for us.
Can you confirm that the BAPI_PO_CHANGE does not support adding
confirmations? We debugged the BAPI and there is no code for updating
confirmations found.
Best regards
Bernhard Lascy
09.08.2011 - 10:43:07 CET - Antwort von SAP
Dear Bernhard,
I regret to inform you that the functionality you request is not
implemented in the R/3 standard system.
Unfortunately it is not possible to change/load confirmations with the
function module BAPI_PO_CREATE/BAPI_PO_CHANGE. Table POCONFIRMATION in
BAPI interface is relevant for Display/List Vendor Confirmation in BAPI,not for update/insert Vendor confirmation in PO.
Furthermore, we recommends that you use Idocs for automatically
entering confirmations. The Message type to use is ORDRSP.
You may read more about this topic in the online documentation.
Please see also following attached note for your reference.
456127 FAQ: Electronic Data Interchange (EDI) in purchasing
Best regards,
Pavel Olysar
Support Consultant
Global Support - Logistics

EDI 850 PO Cancel

I am trying to configure EDI 850 Purchase Order Cancel. I would like to get some advice from an expert here if I am on the right track.
To do this, I am using the action segment in E1EDK01-ACTION:
'001' reverse entire document.
Will the '001' reverse entire document cancel the sales order that corresponds to the PO cancel that is sent?
ps: I will not forget to reward points!! Thanks!

You can't specify reason for rejection for items in a sales order that has subsequent document(delivery doc.). Like you said- this sales order has a delivery status.
If sales order doesn't have a subsequent document, we can cancel it using your suggestion. What about if it has delivery status? How could it be cancelled? Anyone else has done PO Cancel in EDI before? Any help??

Java mapping for EDI order document

hi,
My project is to convert a EDI-850 Purchase Order Document using XI into an R/3 system.I planned t use java mapping So,I had got the java code necessary for the mapping from a tool called ALTOVA XML MAPRFORCE.
I have converted the code into a .jar file and put into the XI server.The mapping is working fine now. If i give an EDI order document as input to the mapping and test the mapping the out put is coming correctly.
Now i dont know what I should do in the Integration directory.
As I have to convert this document and post it in a R/3 system.I have found the function module to create a Purchase Order also "BAPI_PO_CREATE".
What should I do next ?

Hi Mithun,
Follow the steps below:
1. BAPI is a RFC function module. So you import into Integration Repository. Then map your output to the structure of RFC.
2. In the integration Directory,
a. Create a business service representing your source.
b. Create a business system representing your R/3 system.
Before creating business sytem, first you need to register it as a techincal system and business system in sld.
c. Create a Sender Agreement to pick the message from source system. Depending upon the type of source system, you need to configure the sender adapter.
d. Create Receiver determination to route the message to the target system
e. Create interface determination to pick the current Interface mapping to convert source message to target message
f. Create Receiver Agreement to send the message to R/3 System. This should encapsulate Receiver Communication channel which is using IDoc adapter.
Reward if helpful.
Regards,
Suraj Kumar.

EDI in purchasing

Similar Messages

Maybe you are looking for