Skip to Content
avatar image
Former Member

Multimapping : idoc(data,control) to file(3 or 4 based on condn) with ack

Hi Experts,

I am doing Idoc to file scenario, where From ECC System, every 15 min a master data idoc will be generated, after every 5 min of master data idoc created, a corresponding control idoc(Which has the file name and record count) will be created in ECC system. PI will receive the master data idoc and split into 3 different data files(Lets say A,B and C) and send to the target legacy system. once these 3 files arrived to legacy system, it will give a confirmation message to PI, then the corresponding control record need to be sent to the target legacy system from ECC system through PI.

similary the same master data idoc will run once in a day( we can differenciate this idoc with few fields entries) . In this case PI will send a single data file to the target legacy system, once the data file is received, legacy system will send a confirmation message, then PI need to send the corresponding control idoc.

In both the cases the target data file is fixed file format. for both the above conditions need be created as a single scenario.

Please suggest me, how to implement this scenario.

Regards,

Mahakrishnan T.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Feb 19, 2010 at 01:29 PM
    I am doing Idoc to file scenario, 
    once these 3 files arrived to legacy system, it will give a confirmation message to PI,

    FILE does not support acknowledgement, so how is it going to send back the confirmation?

    Looking at your description, a BPM is required in your case.

    Regards,

    Abhishek.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      FORK(two branches) {Receive1 (Master_IDOC) , Receive2 (Control_IDOC)}--> Transformation1 (MasterIDOC_to_FILE) --> BLOCK {ForEach/ ParForEach --> Send (ASYNC..to send req/ file) , Receive(ASYNC..to get the resp)} --> Transformation2 --> Send(Async_ControlData)

      Now if you are flexible/ allowed to choose the end-system, then i would suggest to have a Documentum-type server (can host files and can also support SOAP protocol)..... SOAP will help you in receiving a confirmation for the files that you send

      Accordingly, change the protocol mentioned in the above flow (from File to SOAP)

      In the above flow you will have to do a lot of customization, describing the same would create a messy picture hence didnt do it 😔

      Transformation1 will be IDOCMasterData_FILE ..... and the three files generated will be send by the ForEach/ ParForEach block (for more info refer: /people/milan.thaker/blog/2008/08/05/modes-in-block-step-of-bpm

      Transformation2 will be IDOCControlData_FILE .... and will generate the file to be placed for Control records.

      Fork is mentioned so that you will get Master_Idoc first and then the ControlRecord.

      Regards,

      Abhishek.

      EOD