Differentiate idocs in R3

Hello Folks
I have to send MATMAS idoc from 2 third party systems to R/3 through XI.
In XI, I will do separate message mappings to MATMAS Idoc for each of these. But in R/3, how can I differentiate the Idocs for each third party system.
Thanks

Hi Ricky,
Are you using two different services for each third party in XI?
If Yes, You will have to assign logical system name to each of this third party in adapter specific parameters and then in we20 create partner profile with this logical systems.
This link would be helpful:
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660">https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660</a>
Thanks,
Beena

Similar Messages

How do you differentiate IDOC XML format and ordinary XML format

how do you differentiate IDOC XML format and ordinary XML format since they are used by IDOC adapter and RFC adapter???

Hi,
Cremas Structure starts with Header and followed by Segments...
Normally it begins like this
<CREMAS03><IDOC BEGIN="1">
The second node is Idoc in the header..
Thanks
Anju

IDOC PO Type

Hi
Is there a way by which we can differentiate IDOC coming through EDI or FAX via a third party system?? let me know
Also can we differentiate an IDOC based on PO TYPE??
Thanks

1) First question: Yes there is the way.
Go to Header Sales order>Purchase order data>Purchase order type-->
You can add what ever PO type say
For YEDI-->For EDI.
For Manual and Fax-->DFUE.
If EDI it is EDI Order
map E1EDK14-->"13" PO Type to YEDI(If length is not suffiecient then assign number)
and later maintain this number in table and in user exit look up number and assign number to YEDI.
You can use exit EXIT_SAPLVEDA_001 for lookup. I think mostly not needed.
Also can we differentiate an IDOC based on PO TYPE??
I am not sure exactly what you mean.
For fax order is automatically posted or manual entry ?
"Reward point if usefull"
Thanks,
Narayan

IDOC related question

Hi,
How to extract the content from IDOCs.e.g mautiple idocs are comming.we need to retrive the company ID from all the IDOC.So Please tell me how to extract.
Regards,
Suchitra

Hi Suchitra,
this can be done using BPM were we can differentiate depending upon the company ID value
go to this link it would be helpfull
Posting multiple IDocs with Acknowledgement
https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_weblog&query=multiple+idocs&adv=false&sortby=cm_rnd_rankvalue
Thanx
Sampath

TR-EBS SwiftMT940 mapping to an IDOC message FINSTA01 - Bank Statements

For Treasury, we are going to move to the PI platform. We are currently using EDI.
We start the process by requesting Citibank(GXS operations team) to put a sample file into the outbound mailbox to let our company pick up. The output of the file will be XML.
We will them map and create an IDOC with the FINSTA message.
However, we are only beginning the IDOC mapping process.
Does anyone have a sample crosswalk which will allow us to see how the SwiftMT940 from Citibank can be mapped to an SAP Idoc?
If so, may we see how you mapped the segments?
Also, how do you test the loading of the IDOC created? with the RFEBKA00 program?
Please advise.

Hello,
I am really not sure how you map to IDOC.
But, the following information may be useful to you.
Hello, You can configure the electronic bank statement at the following path: IMG => Financial Accounting => Bank Accounting => Business Transactions => Payment Transactions => Electronic Bank Statement => Make Global Settings for Electronic Bank Statement. All the settings will be done at this path only. 1. Create Account Symbols 2. Assign Accounts to Account Symbols 3. Create keys for posting rules 4. Define posting rules 5. Create transaction type Assign external transaction types to posting rules 6. Assign bank accounts to transaction types. There are different programs to upload electronic bank statement. FF.5 or FF_5. I think your case Multicash format you are using. You need have three files in FF.5 and two files in FF_5 You can prepare a Z program in order to truncate the electronic bank statement into two or three part files and save them on the application server. 1. Take all the external codes list from bank. 2. Take any available documentation from the Bank describing the relevance of the external codes. 3. Make sure that your Chart of Accounts (Bank Accounts) last digits logic is appropriate to meet the requirements. 4. Based on this decide the Account Symbols that are required to be created. 5. Make sure that the masking rules are configured properly. 6. Decide the posting rules that needs to be created. 7. Link up your external symbols provided by the bank with Posting rules and give proper algorithms for posting and clearing logic. 6. Concentrate on the posting areas to be posted while uploading the bank statement. Further explanation would help you to understand the functionality when uploaded the electronic bank statement. Main purpose of uploading the bank statement into SAP is to make your Bank Main Account and physical bank statement balance in sync. You do not have any traditional Bank Reconciliation Statement (BRS) report in SAP. SAP is normally you maintain bank main account and bank sub account. Whenever you make a payment through F-53 or F-58 or F110, the entry would be: Vendor Account Dr To Bank Sub Account The ending digits of the sub-account would be important in configuring the masking rule. Based on this masking rule when you upload the bank statement the entry the system would pass is: Bank Sub Account Dr To Bank Main Account It depends on the configuration, either the sub account will be cleared by the system automatically or you need to run F.13 to clear the sub accounts. At the time of receipts, you have different accounting entries unlike payments. It needs to post to two posting areas. 1. GL Accounting 2. Sub-Ledger Accounting The entries would system itself pass is: Bank Main Account Dr To Bank Sub Account Bank Sub Account Dr To Cutomer account. Clearing logic mentioned for your posting rules and the alogrithm used for your external bank symbols will also play pivotal role in clearing the accounts. Ideally you will use FF67 / FF.5 / FF_5 for uploading manual or electronic bank statement FEBA / FEBA_BANK_STATEMENT is used for furthe rprocessing. GO THROUGH SAP NOTE 48854 Please go through SAP Note. 48854. You will get an idea regarding the functionality of the algorithms. Though this note is in relevant to GB specific, you will find this very useful. description follows below regarding the normal procedure for maintaining table T028G. Due to the different bank codes and posting rules, pre-Customizing is not possible at this point. The following processing types are available - unless stated otherwise, you should use the interpretation algorithm: '000 - No interpretation' in each case. 1. '00': There is no processing. The entry line is ignored. 2. '01': A validation is made whether an entry exists for the transferred check number in the check table (PAYR). The check number and payment document number are transferred for further processing. Interpretation algorithm: outgoing check processing '011'-'013'; the update in the check file is via the interpretation algorithm. 3. '02': Transfer of the ending balance to the electronic bank statement 4. '03': Transfer of the opening balance to the electronic bank statement 5. '04': Clearing via the allocation number which is delivered with the bank statement. No interpretation algorithm. 6. '05': Clearing of BACS payments or BACS bank collection. The reference text field is first read to ascertain whether it involves payments initiated by users or bank collection via BACS. Providing it does involve a cash transaction initiated by the user, the payment document numbers concerned are determined via the reference number and transferred as a reference to further processing. Interpretation algorithm: '000 - No interpretation' or '019 - Reference number DME'. Note To differentiate between the two procedures in table T028G, you have to maintain two separate entries. Example: the bank uses bank code '62' for cash receipts and for BACS bank collection. Ext. Transaction +/- sign Posting rule Int. Algorithm Processing type 62 + GB62 001 5 62 SAPBACS + GB63 000 5 7. '06': Bank costs or interest revenues Recommended interpretation algorithm: '000 - No interpretation' 8. '07': Total amount of cash disbursements 9. '08': Total amount of cash receipts 10. '09': Items not paid Recommended interpretation algorithm: '000 - No interpretation' Regards, Ravi

IDOC to multiple header scenario..

Hi,
My scenario is Idoc to multiple flle scenario..(CDMA & GSM files needs to routed to differient structures)
The requirement is Idoc is triggered at R/3 ECC side, at the target end we have 3 structures, the 1st structure is common as it has email details and the 2nd structure (CDMA structure)and the 3rd structure (GSM Structure) is differient which should handle CDMA & GSM.
so, the IDOC triggers with the following case
1. Only CDMA files
2. Only GSM files
3. Mixed CDMA & GSM files
4. Sometimes missed data without having anyinformation to differentiate (For this case the records should not be geterated)
Ouput should be as follows:
for the first case:
1. If only CDMA files -
> In this case the output should be 2 files (one email file , CDMA text file--- so totally 2 files)
2. If only GSM files -
>In this case the output should be 2 files (one email file , GSM text file--- so totally 2 files)
3. If both CDMA & GSM -
> Then here totally 3 output files where (One email file, CDMA text file, GSM test file -- totally 3 files)
Please throw some light for how to proceed with this type of scenario..
Thanks,
--Kishore

Hi Sarvesh,
The reply was really useful and also can you clarify the below things,
1. I have to drop the files by using dynamic file naming configuration i mean i have to drop the files with the name as below
First case: If only CDMA records in the IDOC then i need to drop 2 files (1 email file -- 1 CDMA text file)
the file names should be as : IDOCNumber_Currentdate.xml -- For email file & IDOCNumber_CurrentDate.txt for CDMA text file
Second case: If only GSM records in the IDOC then i need to drop 2 files (1 email file -- 1 GSM text file)
the file names should be as : IDOCNumber_Currentdate.xml -- For email file & IDOCNumber_CurrentDate.txt for CDMA text file
Third case: If mixed CDMA & GSM records in the IDOC then i need to drop 3 files (1 email file -- 1 CDMA text file & 1 GSM text file)
the file names should be as : IDOCNumber_Currentdate.xml -- For email file & IDOCNumber_CDMA_CurrentDate.txt for CDMA text file, IDOCNumber_GSM_Currentdate.txt)
Here the IDOC number and the text GSM is not used in the ouput structure to use variable substitution method, when we use dynamic file naming configuration UDF then the files are getting overwritten with the first UDF.
Please let me know how to proceed further..
Thanks,
--Kishore
Edited by: Kishore Kumar N.T on Dec 10, 2010 11:33 AM
Edited by: Kishore Kumar N.T on Dec 10, 2010 11:34 AM

Sales x Purchase IDocs

Hi experts,
I have an interface running which sends Sales Order Data from SAP to SQL DB (ORDERS05) online.
I received a request to pull out also purchase data from SAP and push it into the same SQL DB, in different tables.
I tried to figure out which IDoc might be used for this purpose and realized that the same IDoc ORDERS05 can be used for both, Sales data and Purchase data.
Can anyone confirm whether this is correct or not? If not, which one is supposed to be used to achieve that for purchasing data?
If this is correct, can anyone give me some light on how I should configure to have both running online and SENDING data to external system?
I still don't imagine Purchase and Sales Order running in the same IDoc.
Is there any field which identifies the business type (Purchase or Sales Order) or, how am I going to differentiate them?
I really appreciate your suggestions.
Thank you.

Does anyone has any suggestion?
I followed this material:
[http://w w w . saptechnical . com/Tutorials/ALE/AutoIDOCGen/AutomaticIDocGeneration1 . htm]
however, in the step 11, the pop up doesn't show the last option Purchasing Organization, so I cannot complete it. Until there, everything was configured accordingly.
I've also used thread below to guide me through the steps to configure Change Pointers to ORDERS message type of ORDERS05 IDoc. Although it seems to be well configured, when changing a PO in ME22N, no IDocs are NOT being generated.
Auto Trigger DEBMAS IDoc for a customer change
I appreciate all your help.
Edited by: rvsilvax on Jul 12, 2011 9:33 PM

IDoc Error Processing workflow

Invoices are posted from SRM to ECC as IDocs whose message type is BBPIV. When there is an error in the IDoc input such as invalid IO and GL, invalid company code etc., these IDocs will be moved to status 51.
When IDoc is moved to status 51, work item need to be sent to approvers saying this IDoc has an error and need to be corrected. For this a workflow task needs to be developed.
In our system, there are two types of IDoc invoices sent to ECC. One is of type INVOIC01 and another is of type BBPIV01. There already exists a standard task TS00008057 which is activated for the event INPUTERROROCCURREDMM for IDOCINVOIC object type.
I shouldn't use the same event (INPUTERROROCCURREDMM) and IDoc object type(IDOCINVOIC) for BBPIV01, because responsible agents for both type of invoices are different in our company.
Please help us in getting this resolved. Also let me know if my approach is wrong towards this problem.
Thanks,
Rajesh

Hi Rajesh,
Using the same BOR object and event for two different idoc types is not necessarily wrong. There are ways to differentiate the responsible agents based on the idoc type if needed.
Here is how I would solve this:
Prerequisite: you need to make sure that event IDOCINVOIC.INPUTERROROCCURREDMM is triggered when your BBPIV01 iDoc is in error. To check that, you can activate the event trace and test your idoc (activate with tx SWELS, display with tx SWEL).
If the event does not trigger then you need to find out which event is getting triggered (using the event trace as well).
Now the serious business:
1. Create a copy of standard task TS00008057 that will be used for when BBPIV01 iDocs are in error.
2. Link this task to your event IDOCINVOIC.INPUTERROROCCURREDMM in transaction SWETYPV
3. Check in SWO1 if you have an attribute that gives the idoc type (or anything else which you can use to determine wich workflow should start in each case).
If not you need to create a subtype of IDOCINVOIC and in the subtype create an attribute that returns the iDoc type. Then you would need to delegate IDOCINVOIC to your subtype.
4. Create start conditions (tx SWB_COND) in which you check that TS00008057 starts only when idoctype is INVOIC01 and your new task starts only when idoc type is BBPIV01.
Cheers,
Patrick

Idoc to filesplit scenario..

Hi Experts,
Mine is Idoc to file scenario..
Actually Idoc has 2 records where receipt and ship, the receipt record should be sent as it is and ship record should be duplicated to repair and also ship should be sent to ftp..
So finally ftp contains 1 receipt file and 1 repair file and 1 ship file, i am unable to understand how the duplicate file should be created and regarding with mapping how to differentiate b/w this receipt mapping and ship mapping do we need to create two mappings else is it poosible to handle in single mapping..
The other requirement in the scenario was the files in ftp should be in the sequence i.e first Receipt file should be droped and then the repair file followed with ship file.. how to specify this condition ..
any idea regarding with this scenario will be relially appreciable..
regards,
sai

You will need a 1:n mapping. [ 1 Msg for Receipt, 1 Msg for Repair, 1 Msg for Ship]
In Interface determination, use Maintain Order at Runtime checkbox. This will ensure that the messages (Receipt, Repair & ship) will be received at FTP in the same Order.
http://help.sap.com/saphelp_nw04/helpdata/en/42/ea20e737f33ee9e10000000a1553f7/content.htm
- Siva Maranani

Business system name important for IDoc scenario message routing?

Hello all,
I have following problem.
I have to setup with our client an IDoc scenario which is a little difficult.
The client sends project IDocs from Client ERP system to his own XI system next to our XI sytem and at last Internal Order IDocs to our ERP system. We use for each environments (DEV, TEST, PROD) a separately SLD, the client a central SLD. In each environments we use the same business name for our XI system "BS_XI". Now the problem. The client aren't able to configure two times the same business name "BS_XI" for routing to our TEST respective Production environment. DEV will not used. I know the B2B scenario should be used in this case but i have no chance to think about this. Manager decision!
So what can be the workaround.
I think about to provide our client a different Business system name "BS_XI_PROD" with different technical system informations for our PROD environment. So for my understanding, the business system name is unimportant in this case, important here the technical informations which you are able to see in "Display Adapter-Specific Identifiers". Technical system, Port and RFC configuration.
The namings convention for Business system is unimportant in this case, yes?
Many thanks in advance!
Regards,
Jochen

Dear Jochen,
Can you please clarify a bit? Is it a problem between customer's XI system and your XI system?
I think you can use Parties here. In the Party you can define some additional identifiers, with which you can differentiate the incoming IDocs.
(e.g.: in the identifiers tab, Agency=BS_XI, Scheme=ALE#KU (defined in the customer's partner profile), Name=a defined name in the IDoc control record)
So with this you will have a "Business System+Party" as an identifier, where you can use several parties with the same business system.
I hope it helps!
Regards,
Andras

Using same Idoc type & Message type for 2 Interfaces

Hi all,
we have 2 interfaces which uses same Idoc type, message type & Partner No.Only Process code is going to different according to the posting logic.
How can we differentiate both while posting idocs to not mess up each other .
Regards

Hi all,
Say example:
Interface 1 is invoice coming from legacy system to SAP and i have to use AAA.BBB Idoc
Interfaces 2 is accrual coming from legacy system to SAP and i have to use AAA.BBB Idoc
So i am creating partner No with LS_LEGACY and with 2 inbound entries one for each.
Even though i am using the same Idoc types but inside those the process codes are different because they are different in posting logic.
Issue:
From XI perspective i can't differentiate them saying like Invoice interface should execute the entry in the partner profile with invoice process code and accrual interface with accrual process code.
My Idea is to design like this...
Using the Message Code option, While creating partner profile give the MESCODE and in Mapping provide the same MESCODE.
So that even thought i am using the same partner No with same message type & basis types for 2 scenarios, the right interface will trigger the right process code based on the MESCODE mentioned in mapping by carrying the control record values
Please let me know ur views
Regards

IDoc type "DELVRY03" for INBOUND delivery confirmation and Outbound Deliver

Hi ,
We have a requirement where we have to send Inbound delivery confirmation as well as outbound delivery notification to our same customer. (3PL case)
We have a EDI partner who is receiving our messages and transforming them before sending it to customer.
Now my problem is , since I am using same idoc type (DELVRY03) for both cases therefore wondering how my EDI partner will differentiate whether received message is a INBOUND delivery confirmation or OUTBound delivery notification.
regards
Shrey

Thx for your reply ...
Wondering about the impacts , if I create a new message type like ZDESADV and attach it to DELVRY03.
In this i could have two message types DESADV and ZDESADV.
Will it impact anywhere ?
Regards
Shrey

Idoc processing - determine Basic Type in Program

Hi Forums,
I would like to determine the Basic type that is being processed by at the time of my Idoc creation.
the function module I am using is being called by shipping document as well as delivery documents.
I would like my code only to be executed when it is a basic type of DELVRY05

Hi,
1) Goto Tcode - we57:
Assign function module to IDoc type
Module: Function module
Basic type:
Message type:
Direction: 2 (inbound)
This will differentiate between Shipping and Delivery.
2) Creating Inbound process code - we42
For Outbound Process Code -- WE41.
For further plz refer following link.
https://wiki.sdn.sap.com/wiki/display/ABAP/ALE%2CIDOC
Thanks and Regards,
ShreeMohan

Ale/idoc setting

Please use more informative subjects in future. How are we supposed to differentiate between your questions when you keep using the same subject?
hi folks
i am working on outboung idoc...here in the settings part when i created a port and gave the port name in the partnerprofile its giving the message please enter a value for package size.
could someone let me know exact way of setting the configuration....
i am working on sending vendor data i.e. message type is cremas...i hv extended this.
thanks in advance
Edited by: Matt on Mar 23, 2009 2:13 PM

you can find the below example of idoc setting for out bound
A. First of all, we need to identify the Transaction Data which is required to be Transfered to external System.(Ex: Sales Order Data or Shipment Data or Delivery Related Data).
B. Secondly, Identify the IDoc Type & Message Type. IDoc Type can be found in Transaction WE30 & Message Type Can be explored in Transaction WE81.
C. After that, assign the IDoc Type to Message Type in WE82.
D. Identify the Selection Program (Outbound) which is generally a Function Module in the Form of IDOC_OUTPUT_<Message Type>. Example, if the Message Type is ORDERS, the FM will be IDOC_OUTPUT_ORDERS.
E. Assign the Function Module to a Process Code in WE41 (Process Code for Outbound).
F. Configure Port Definitions in WE21 for which the RFC destinations are to be maintained in Transaction SM59.
G. Maintain Partner Profiles for the Outbound Message Processing in WE20.
H. Last, but not the Least, we need to Focus Mainly on Message Control Configuration which is nothing but maintaining the Output Type for the Outbound IDoc to be Triggered for the Sales Order Application or Delivery Application.
i. In Message Control Configuration, we'll maintain
1. Condition Tables
2. Access Sequences
3. Output Types
ii. To Create the above elements, we can go to SPRO Transaction and do the same depending on the Application Area such as Sales / Shipping / Logistics Execution etc.
iii. For Output Types & Access Sequences, we can go to the Transaction NACE or VK01 in which we'll maintain the Output Types / Access Sequences & Condition Records.
Please note that all the above steps may not be needed if we are using some of the Standard Elements provided by SAP such as Message Type, Process Code, IDoc Type & Selection Program as many of the Standard SAP Applications have their own Elements for different Application Areas.
For example, if you want to send an Order Confirmation IDoc when the Sales Order is saved, you can use the Message Type ORDRSP, IDoc Type ORDERS05 & Selection Program as IDOC_OUTPUT_ORDRSP.

If I have Multiple recever R/3 systems of same idoc structure receiver?

If I have 3 receiver R/3 systems of same recever IDOC structre...can I import only one idoc or can I import 3 idocs from 3 R/3 systems? If I import only one idoc ..then is control record differ for other R/3 systems,.,,? Plz clarify my doubt...thanq.

You can import one structure from the same R/3 systems so far as:
- no modifications/extensions to the IDOC
- you dont plan on mapping the header data in your interface mapping.
- IDOC release is the same and as such no subtle differences in the back end systems you are working with
Procedure
- Import the idoc from system - also load meta data in ABAP side
- perform all your mappings
***- if mappings are the same and only difference is the control record, use same mapping and disable the control record in mapping
***- if above (mapping same), use the same receiver determination and differentiate destination by receiver agreement/channel
- if mappings are different use seperate interface determinations.
sincerely,
--NM

Differentiate idocs in R3

Similar Messages

Maybe you are looking for