Flat IDoc to Retail backend system

Hello,
I have a flat file, representing ORDERS01 IDoc transaction. Part of the file is listed below as an example. On the back-end I have a SAP Retail Management System, that should consume this purchase order and do something with it.
Question: how to do that in the most easy way?
From what I was told SAP Retail system can only receive data through RFC or IDoc channels. Is there any way to just pick up this file from the local system and send using IDoc or RFC adapter not defining any mapping, but just letting Retail system to parse and understand the data?
If there is any example for such case, I'll appreciate the link.
Thanks,
Maxim.
Example of the Flat IDoc ORDERS01 file -
EDI_DC40                           2   ORDERS ...
E2EDK01003                                                         USD   1.00000 ...
E2EDK14                                                        008BIC...
E2EDK14                                                        00600 ...
E2EDK14                                                        00702     ...
E2EDK14                                                        012ZOR    ...
E2EDKA1002                                                     AG 000024588        xxx              ...

Hi Maxim,
>>That's not exactly what I was looking for. The article shows how to translate Flat IDoc to XML. I'm looking for something different.
I guess that is th blog you should refer. I will explain why...
>>I have a Retail back-end system that can consume Flat IDoc, which I have. However, I'm curious how to transfer the IDoc file sitting on the filesystem to that remote Retail system through the IDoc adapter.
Picking the flat IDOC from Retail can be done by File Adapter and then using the modules (as per the blog), the flat Idoc will be converted to XML Idoc so that XI can understand the structure.
Now by using a Receiver IDoc adapter this XMLized Idoc is again send to the remote Retail system.
Hope this is clear now
Regards
Suraj

Similar Messages

Create IDOC Type ORDERS in BackEnd System

Hello together,
we use " extended classic scenario" in our SRM 4.0 and replicate PO's in the ECC 6.0 ERP Backend System. We would like create during the replicat a Message Type (IDOC) ORDERS in Backen System. I háve customized (NACE / MN05) but it is not poosible to generate a IDOC. I have read it is necessary to activate a USER-EXIT for BBP PO's.
My question:
Which USER-EXIT and how must i create this!
Thanks for Answer!
Regards,
didisap
Edited by: Dietmar Blome on Feb 8, 2011 11:59 AM
Edited by: Dietmar Blome on Feb 8, 2011 12:01 PM

Hi,
Pls refer to following links for sample code ->
Re: Status distribution incorrect in GOA
Re: Distribution of GOA in R/3
Re: GOA Distribution SRM 5.0-ECC 6.0 - Account Category & Multiple Distribution
Re: Source determination in backend (R/3) for distributed contract i.e. GOA
FM or BADI s' used to create a GOA
BR,
Disha.
Do reward full points for useful answers and close the thread if your query is answered.

How can we save multiple IDocs as a single Flat file in R/3 system ?

Hi,
How can we save Multiple Idocs as a single Flat IDoc in R/3 (Not xmlized)
Kulwinder

Hi,
Check this link for Mutiple IDOCs into single File.
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
Regards,
phani
Reward points if Helpful:)

Error while posting return delivery to backend system

Hi All,
We are facing problem when we are posting return delivery. Currently we are in ECS implementation. Our SRM is 7.0 EHP3.
Scenario goes as, SC is created then PO is created then further confirmation is created and on creating return delivery of this confirmation, this return delivery goes error in process.
Now on further analyzing, I found out that outbound IDoc in SRM is getting posted successfully but when ECC receives this IDoc it is saying please enter reason for movement 122. This reason for return is already entered while creating the return delivery. But this reason is not flowing in IDoc (Message Type MBGMCR and Basic Type MBGMCR01) in SRM and further to ECC. This field MOVE_REAS in IDoc is populating blank.
Can anybody help me resolving this problem? Any pointers or SAP notes related to can also be suggested.
Thanks
Siddarth

Hi Siddarth,
Please implement the note below, which is included in SP05.
2007628 - Return delivery cannot be posted in backend system as reason for return delivery is empty
Regards,
Wendy

Goods Receipt not transferred to the Backend System R/3

We are currently using BBPCRM4.0 & SAP R/3 4.7 (extended scenario)
For a particular Purchase Order which has a material number, We cannot transfer GR to the Backend System R/3 successfully.(The shopping cart of unsuccessfully transferred GR is created by using material)
When I check R/3 using WE05, I can find the message "The plant data of the material G09002202 is locked by the user MRP_RFC". This must be the reason why GR is not transferred successfully to the Backend System, but I do not know what this message mean.(As you see, MRP_RFC is the user name that connects SRM and R/3. + That moment the material is not locked by any user in R/3)
If we try to create the GR document again in SRM, the message "Item is already being processed" is shown, so cannot make BUS2203 Docs.
To sort out this, we remove the GR Transfer Error Information in
BBP_DOCUMENT_TAB.
After removing the information of this error in BBP_DOCUMENT_TAB, surprisingly we can make GR successfully.
Weird!.
Only for a particular PO which has a material, but not everytime.
Sometimes this problem happens.
At the first time, it doesn't work, but after removing the data from BBP_DOCUMENT_TAB, when we try GR again it works.
Could you help me why this symptom happends..?
Edited by: Hyangsook Moon on Feb 28, 2008 6:44 AM

Hi Hyangsook Moon,
The system is allowing you to create Confirmation again in SRM because the status is not yet updated in SRM since the G.R is not created in the backend successfully.
Since the confirmation is created in SRM and could not able to create G.R in R/3 through IDOC the system is giving you message as " Document is being processed".
So the system is allowing you to create confirmation again once you delete the table entry.
Hope this makes you more clear.Clarifications are welcome.
Award points for helpful answers.
Rgds,
Teja

Get IDoc-number from flat IDoc using dynamic configuration

Dear experts
In an IDoc2File scenario I have added the IDoc-number to dynamic configuration using the folling code in an UDF:
DynamicConfiguration conf = (DynamicConfiguration)
container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey FileName = DynamicConfigurationKey.create("http:/"+"/sap.com/xi/XI/System/File","DOCNUM");
conf.put(FileName, a);
The information is stored in the SOAP message
<SAP:DynamicConfiguration SOAP:mustUnderstand="1">
<SAP:Record namespace="http://sap.com/xi/XI/System/File" name="DOCNUM">0000000000012345</SAP:Record>
</SAP:DynamicConfiguration>
Can anybody tell me how I can access this information in the "variable substitution" section of the CC? Perhaps something like "message:docnum"?
Additional information:
Taking the IDoc-number from the payload using e.g. "payload:ORDERS05,1,IDOC,1,EDI_DC40,1,DOCNUM,1" does not work, since the XML-IDoc has been converted to an flat-IDoc.
Thanks in advance for any good ideas
Markus

Dear Rodrigo and Sarvesh
Thanks for your help so far! I applied your hints and now it is working fine.
But now I have the following additional questions
1.) My message mapping only maps the input IDoc to an output IDoc of the same type and structure. The MM is only required to process the UDF. Is there another, better solution to achieve my requirement that the IDoc-number shall be part of the filename?
2.) In the CC you have the possibility to use temporary files (section "Processing", Option "Put File" = "Use Temporary File". I think this will not work with the given solution, will it?
To possibly help somebody else or clarify the mechanism once again, I wrote down how my solution now looks like.
My UDF in the message-mapping looks like this
- Input = DOCNUM of IDoc, e.g. ORDERS05/IDOC/EDIDC/DOCNUM
- Outpt = DOCNUM of IDoc, e.g. ORDERS05/IDOC/EDIDC/DOCNUM
- UDF:
public String putDynamicConfiguration(String docnum, Container container) throws StreamTransformationException{
try
     DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
     DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
     String filename = "Prefix_" + docnum + ".txt";
     conf.put(key, filename);
     return docnum;
catch (Exception e)
     return docnum;
In the CC the settings are now as follows
File Name Scheme = . -> only a dot or something else, because this field is obligatory, even if it is not used in this case.
Variable substitution (...)
    Enable -> unchecked
Adapter-Specific Message Attributes
    Use Adapter-Specific Message Attributes -> checked
    Fail If Adapter-Specific Message Attributes Missing -> checked
    File Name -> checked
    Directory, File Type, Temporary Name Scheme for Target File Name -> unchecked
When I send an IDoc to PI and view the Adapte-Engine Version of the message (the SOAP-document, not the payload) I can find the Filename:
<SAP:DynamicConfiguration SOAP:mustUnderstand="1">
<SAP:Record namespace="http://sap.com/xi/XI/System/File" name="FileName">Prefix_0000000000012345.txt</SAP:Record>
</SAP:DynamicConfiguration>

One IDOC sent but 8 IDOCs received in backend

Hi,
I have a strange problem:
I generate a IDOC at the end of a simple BPM (receive message, send same message, no transformation step). In sxmb_moni, I can see one message (from process engine to IDOC adapter) as expected. When I click on "IDOC"-field in the message row (sxmb_moni), I can see that 8 identical IDOCs (only different IDOC numbers) were generated and in the SAP Backend system, I also receive 8 IDOCs.
This effect sometimes appears, sometimes not. I cannot see why or why not.
Has anyone an idea where I could search to stop this phenomen?
Kind regards,
Torsten

Hi Bhavsh,
no, I'm not using a collect pattern. BPM simple consists of one receive step and one send step.
I don't think that there are any Packaging settings on XI, because it worked already for a long time and we didn't change settings.
Or could Packaging settings in the backend system influence the XI?
But I got a step further: If I double-click on one of these IDOC messages in IDX5, I can see a lot of error status entries (6x status 51, 2x status 54). Is it possible that XI sends an IDOC multiple times if an error occurs?
Kind regards,
Torsten

VC Report design - Data from 2 backend systems

Hi,
I have a report to develop at below.
Material Inventory (Backend 1) Inventory (Backend 2)
XYZ 10 12
ABC 100 103
and so on.
I get the following from 1st backend system
Material and Inventory (Backend 1)
I get the following from 1st backend system
Material and Inventory (Backend 2)
Master data from both systems are syncronised that means that the material numbers will be the same.
I am using VC to extract data from these systems, I have managed to get the data into 2 table views and now need to join them together into 1 view as shown above.
The combie operator does not work as it shows the data as below
XYZ 10
XYZ 12
ABC 100
ABC 103
Please suggest options.
Regards,
Deepak

thanks a ton Srinivas
so to understand logic clearly---
Q1- if i have 2 cubes- cube1 with flat file data and cube2 with sap data
and if i build Multiprovider on top of it - the data will be like below ?
Order No....level....date....quantity...price....dist.channel....country.
131.............1..........1.1.10.......4........##.......11..............US
131.............1..........##...........##.........100.......11.............##
131.............2..........2.1.10.......5.........0........11..............US
131.............3..........2.1.10.......1.........0........11..............US
231.............1..........1.1.10.......4.........0........11..............Uk
231.............2..........##...........##.........600.......11.............##
231.............2..........2.1.10.......5.........##........11..............Uk
231.............3..........2.1.10.......1........0.........11..............Uk
and to bring the clear data i have to MANUALLY seperate logic of CONSTANT SELECTION in all queries in future ??
Q2- if i have 1 dso with Order no. and Line item & Distribution channel as key, and two transfer rules , 1 with flat file and 1 with sap
the data in cube will be like below ??
Order No....level....date....quantity...price....dist.channel....country.
131.............1..........1.1.10.......4........100.....11..............US
131.............2..........2.1.10.......5.........0........11..............US
131.............3..........2.1.10.......1.........0........11..............US
231.............1..........1.1.10.......4.........0........11..............Uk
231.............2..........2.1.10.......5..........600...11..............Uk
231.............3..........2.1.10.......1........0.........11..............Uk

Flat-Idocs via the IDOC-adapter

Hi All,
I want to send a flat-IDOC via the IDOC Adapter to a SAP R/3 system. The IDOC adapter does not accept flat-IDOC, but wants xml-IDOC. Does anyone know how to send this flat-IDOC to the SAP R/3 via ALE, but without XML-lizing the IDOC?
I am looking in to the principle of tunneling, but that will involve some ABAP coding.
Cheers,
Frank

Hi Bhavesh,
I tried, but the IDOC adapter wants XML. The receiver IDOC adapter checks the type of the payload and determines if IDOC tunneling is used or not. I don't know yet how to change the type of the payload:
<i>method CL_IDX_IDOC_SERVICE-GET_PAYLOAD, part of package SIDOC_ADAPTER
test if idoc is in tunnel-payload-format
    l_content_type = l_payload->getcontenttype( ).
    IF l_content_type = if_xms_resource=>mimetype_idoc.
      l_idoc_resource ?= l_payload->getdata( ).
      l_tunnel_flag    = 'X'.
    ELSE.</i>
and with tunneling the idoc must be stored in certain tables where the receiver idoc adapter will get the IDOC instead of the payload. And our flat-idoc is in the actual payload. So the direction I am looking into is an abap mapping, which will change the payload type and stores the flat idoc in these tables, so the idoc adapter is "fooled" to believe it is IDOC tunneling.
Cheers,
Frank

Flat Idoc and receiver determination

Hi Folks,
I have a scenario in which the Idoc is sent to XI in a flat format (Flat Idoc) using tunneling mechanism. The receiver determination configured is conditional based (Verifies the values in the specified fields of the Idoc).
Now my question is as we know flat Idoc doesn't contain any fields like XML in the input payload, how the receiver can be identified?
Reminder: (Receiver determination is conditional based and verifies some field values in the Idoc structure)
Thanks,
SPMD

Hi Shabbirmdpasha,
You can use file adapter channel to get idoc flatfile and convert to xml idoc in the module of the file adapter (available in PI 7.1). You only need to make a relation with the type of idoc with the name of the file: for example, DESADV_xxxxxx.txt for all files with DESADV flatfile idoc's.
With this method, you know the interface of the outbound interface, and in the receiver determination you can check in the header of the idoc (dc40) to determine the target system.
PD: Sorry for me english...
Edited by: Oscar Navas on Dec 1, 2010 4:11 PM

Distribution of GOA to the backend system

Dear Experts,
I am working in Extended classic scenario (SRM 5.0). We are planing to configure GOA.
Can any one give me the steps required to configure GOA and distribute the contracts to the back end system.
When I create the GOA as of now GOA is getting created but not distributed.
Regards,
B.N.Karthikeyan

Hi,
Here are the main configuration steps needed:
1: Make sure you have done the following in customizing:
   When you go to define transaction type and you
   choose the entry with BUS2000113, then you click Transaction type
   go to DETAIL screen of GCTR and choose Global Outline
   agreement as a specification.
2: You can follow these steps.
   1. Go to the transaction WEDI
   2. Goto IDoc menu and select Partner Profile (or F6)
   3. In Partner Profile, Goto PartnerType LS
   4. Click on the client eg. ABCCLNT300
   5. In "Inbound parmtrs" make an entry for BLAORD.Enter the client as
   Partner number. BLAO as Process Code.
3: In the R3 backend system,
   maintain BLAORD as inbound message type, and maintain
   BLAREL as outbound message type
4: One of the requirements for setting up GOA is:
   Mapping of the appropriate products,product categories, condition
   types, document IDs, transaction types and text iDs in the BAdis:
   *IN EBP > BBP_CTR_BE_CREATE
IN the backend system: BBP_CTR
Any GOA contract in EBP has to be mapped in R/3 with the corresponding
entry for conditions i.e 01CT to synchronise the two systems.
If the conditions are not mapped, the idocs will not be created.
Hence, please map the conditions and check for the distribution.
It is also an option to try:
Please run the function module 'BBP_PD_CTR_TRANSFER', this FM posts the
IDOC in R/3 and add an entry in BBP_DOCUMENT_TAB,
afterwards call report 'CLEAN_REQREQ_UP' which updates the status.
Kindly ensure all customizing and settings are correct in both SRM and
R/3 backend in order for the GOA to pass from systems without issues.
I hope this helps,
Kind Regards,
Lisa

PO confirmation from Customer Backend System

Dear experts,
I'm implementing SMI scenario with SAP SNC 5.1. I was traying to send a PO confirmation from Custoemr Backend system (ECC) to SNC.
The process is this:
1) Supplier creates and publish a Replenishment Order in SNC
2) SNC sends to Custoemr backend system (ECC) the message VendorGeneratedOrderNotification.XML that is converted by SAP PI in to ORDERSP.ORDERS05 message.
3) Customer backend system (ECC) receives this message and creates the PO.
4) Customer backend system sends a message to SNC to confirm the PO creation.
My question is about point 4, for this communication I'm using VendorGeneratedOrderConfirmation.XML (as described here http://help.sap.com/saphelp_scm2007/helpdata/en/46/77adcbf9cf0ad3e10000000a11466f/content.htm ), the IDOC I'm using is ORDRSP.ORDERS05 but I have a problem with mapping because there are some data missing.
Is this combination ( ORDRSP.ORDERS05 > VendorGeneratedOrderConfirmation.XML ) correct for this type of communication?
If not what kind of message should I use to send a PO confirmation from Customer backend system to SNC?
Thank you in advance for your support.

Hi Team,
RO confirmation in SNC should be done with ReplenishmentOrderConfirmation_In as this is done by customer.
If you see in help link
VendorGeneratedOrderConfirmation
The customer back-end system sends a purchase order confirmation to SAP SNC. This is used, for example, when SAP SNC awaits purchase order number assignment from the customer back-end system.
VendorGeneratedOrderConfirmation is used when SNC needs purchase order number assignment.
Regards,
Nikhil

SUS - Multiple backend systems (MM & SRM)

Hi
I am implementing a SUS client linked to both SRM (seperate client) and MM.
SAP refer to this as the 1:n scenario http://help.sap.com/saphelp_srm50/helpdata/en/cd/0e343e47fd6b2ee10000000a114084/frameset.htm
All interfaces are working correctly except for SUS PO confirmation --> Backend.
For MM-SUS the PO confirmation message route is:
SUS to PI - PurchaseOrderConfirmation_Out
PI to ERP - ORDRSP.ORDERS02 idoc
For SRM-SUS the PO confirmation message route is:
SUS to PI - PurchaseOrderConfirmation_Out
PI to SRM - PurchaseOrderConfirmation_In
The problem we have is getting PI to send the appropriate message back to the appropriate backend system.
Has anyone implemented this scenario?
If so can you explain how PI deals with this?
Do we need 2 interfaces in place?
Thanks
James
Edited by: J-Wilson on Jan 19, 2012 1:25 PM

thats something to do with PI.
they get source XML from SUS. and in PI after deciding target system they have to decide the target. I dont have that much knowledge on PI but i know that they have a place in the integration builder to pass the condition for a field from XML. according to that they need to decide the target interface..
i think SAP must have provided guidelines for PI to configure for SUS.

Error when retrieving all backend systems SPS12

After upgrade system to SPS12, there was a error in UME:
"An unexpected error occurred when retrieving all backend systems available for user mapping."
Does anyone given this error?
#1.5 #003048323AFA006A0000004700005F10000438C0C2A59F50#1188300457345#com.sap.security.core.wd.assignusermapping.AssignUserMappingComp#sap.com/tcwddispwda#com.sap.security.core.wd.assignusermapping.AssignUserMappingComp#adm2#577##srv.retail.com_DEP_34251450#adm2#a5fdb470555911dc85f8003048323afa#SAPEngine_Application_Thread[impl:3]_22##0#0#Error##Java###An unexpected error occurred during retrieval of all backend systems available for user mapping for principal ''''.
[EXCEPTION]
#2#USER.PRIVATE_DATASOURCE.un:adm3#com.sap.security.core.wd.exception.UmeUiException: java.lang.NoSuchMethodError
     at com.sap.security.core.wd.umeuifactory.UmeUiFactoryCompInterface.handleThrowable(UmeUiFactoryCompInterface.java:2865)
     at com.sap.security.core.wd.umeuifactory.UmeUiFactoryCompInterface.getUserMappingSystems(UmeUiFactoryCompInterface.java:1671)
     at com.sap.security.core.wd.umeuifactory.wdp.InternalUmeUiFactoryCompInterface.getUserMappingSystems(InternalUmeUiFactoryCompInterface.java:605)
     at com.sap.security.core.wd.umeuifactory.wdp.InternalUmeUiFactoryCompInterface$External.getUserMappingSystems(InternalUmeUiFactoryCompInterface.java:982)
     at com.sap.security.core.wd.assignusermapping.AssignUserMappingComp.refreshSystems(AssignUserMappingComp.java:339)
     at com.sap.security.core.wd.assignusermapping.AssignUserMappingComp.setPrincipal(AssignUserMappingComp.java:288)
     at com.sap.security.core.wd.assignusermapping.wdp.InternalAssignUserMappingComp.setPrincipal(InternalAssignUserMappingComp.java:230)
     at com.sap.security.core.wd.assignusermapping.AssignUserMappingCompInterface.resetComponent(AssignUserMappingCompInterface.java:139)
     at com.sap.security.core.wd.assignusermapping.wdp.InternalAssignUserMappingCompInterface.resetComponent(InternalAssignUserMappingCompInterface.java:136)
     at
Message was edited by:
        Alexander Ardashov

Hi Alexander,
The exception "java.lang.NoSuchMethodError" means that a Java method has been called which does not exist.
Only two possibilities:
a) Your upgrade was only partial successful
b) A bug by SAP
I would consider to reinstall SP12 and if it still doesn't work, open an OSS message.
Hope it helps
Detlev

Transfer Material Master (MATMAS) Idoc into Retail Article Master (ARTMAS)

I need to transfer data from an SAP 4.7 ERP system that is set up for material masters to a different SAP 6.0 system that is set up as Retail.
The question is which system should be doing the conversion to the ARTMAS
Option 1: The outbound IDOC would be a MATMAS05 and it would be recieved and converted on the Retail side to an ARTMAS doc to create the articles.
If this is the case do you know how this needs to be set up on the retail side, for this conversion to occur.
Option 2: Translate the material master and send out an ARTMAS IDOC from the ERP system In this case I think that we will need a lot of custom code, and the SAP sending box will need to perform conversions that are known only on the retail side.
I am not really asking for the exact configuration set up
What I am looking for is how if other companies are doing this which option is considered the standard/best practice

Question was never answered we will need to determine how best to do this.

Flat IDoc to Retail backend system

Similar Messages

Maybe you are looking for