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

Similar Messages

Batches not getting updated by incoming idoc DELVRY03 (message type SHPCON)

Hi
    I am using incoming idoc DELVRY03 (message type SHPCON) to update delivery document.I am using field E1EDL24-CHARG to pass batch data.
      However batch number is not getting updated in delivery document. I have verified aspects like batch number is valid etc.
     While updating batch number thru incoming idoc, do I need to supply some other data?
Please help.
TIA
Koustav

Hi Biswas,
I think batches are determined automatically in the deliveries while creation and thats the reason it is not getting the batch number in the delivery, if there is no automatic batch dertermination then it will update the valid batch number
also please check the batch determination procedure and the batch master in MSC2N and availability of materials for that particular batch
regards,
Santsoh

Idoc type, message type and process code for EDI 940 & 945

Hi,
We are implementing a scenario wherein we are required to send a Wharehouse Shipping Order to the warehouse (forwarding agent) using EDI 940. The output of the o/b is triggered from the Delivery (VA01) after creation of a Delivery in SAP. Once the warehouse ships the goods, it notifies us back by sending EDI 945 (Warehouse Shipping Advice). Using this inbound 945 we are required to update the existing delivery in SAP, i.e., it should do the Pick, Pack and PGI.
Can someone tell me which Idoc type, Message Type and Process code should be used for the above scenario.
Thanks in advance for the help.
Regards,
Gajendra

Hi Gajendra,
For EDI940, you can use message type SHPORD or WHSORD, IDOC type DELVRY01 and process code DELV.
For EDI945, you can use message type SHPCON or WHSCON, IDoc type DELVRY01 and process code DELV.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

Possible? Using External Definitions for data type/message type definitions

Hi all,
i want to use external definitons in my own data type definitions. Is that possible? And if yes, how?
I imported many definitions via a mass import. Now I also want to use these definitions for further interfaces (than the imported ones). The most convenient would be of course to just use them as a custom created type. Can I somehow "convert" an external definition to a data type/message type?
KR
Felix

Hello Felix,
The External defination which you has been imported that cant use in DT and MT but yeah you can use this in Service interface.
you cant modify that External defination if you want to do that then 1st of all modify it and then reimport it as an another external defination.
and creating service interface with this ED you can use it in your message mapping .
i hope this will help to you to clear your doubt.
Monica

Nhi guru's cross apps what is basic type,idoc type , message type

nhi guru's cross apps what is basic type,idoc type , message type plz help me i am larning how to work on idocs using ale explain me like realtime environment

Hi,
Hi,
i got this data from sdn .plz go thru might be helpful
IDOC is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
how to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
For creating a IDOC u need to Create a segment type in WE31.The internal table in which we store the data to be passed to the IDOc thos fielda are defined in fieldname and data element.Save and release the segment.
Create IDOC type in WE30. Give min and max types. Mark it as mandatory.
Create Message type in WE81.Assign it to a change request and save it.
Link this message type with IDOC type in WE82.
Then start your coding and pass the details of Data and control records.
Just have a look at these links:
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
Creation of IDOC:
idoc creation
https://www.sdn.sap.com/irj/sdn/advancedsearch?query=creation%20of%20idoc&cat=sdn_all&start=11
ALE/ IDOChttp://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
i think this will helps u
reward is usefull

Error while trying to post inbound idoc of message type COND_A

Hi,
I am getting error while trying to post inbound idoc of message type COND_A.
If I left Usage & Condition field of segment E1KOMG then 'Table not available' idoc message is coming
and if providing value in above fields then dump is coming.
How to solve ?
Plz do reply
Thanks
Mohit

I do not see any reason why you would need to use COND_A04 if COND_A01 is working.
What if you could get COND_A04 to post and you would face the same result as in COND_A01?
If SAP does not check wrong values, then you have to do it yourself, or you report an incident at SAP (after you have searched for OSS notes that may have fixed this error already)
For example OSS Note 1169998 - IDoc: KONP-LIFNR values not checked
fixed a situation where the vendor number was not validated.

Diff bet IDOC and Message Types.

What are the difference between IDOC and Message types.
Diff between MATMAS01 ,MATMAS02 and MATMAS03

IDOCs:
- IDOC is an Intermediate Document. It is simply a data container used to exchange information between any two processes that can understand the syntax and semantics of the data.
An IDOC is created as a result of executing an Outbound ALE or EDI process.
In an inbound ALE or EDI process, an IDOC serves as input to create an application document. When an IDOC is created in the system , an unique number(16 Digits) is assigned to it.IDOC will wait until the Remote System is Active.
Basic Idoc Type: Basic Idoc type defines the structure and format of the business document
that is to be exchanged between two systems. Basic Idoc type can refer to an SAP provided
basic IDOC type or a customer developed basic IDOC type.
- A basic IDOC type has the following characteristics:
Name : A basic Idoc type can be assigned upto a thirty character name.
List of permitted segments: The segments make up the IDOC structure.
Hierarchy of segments : The hierarchy of segments specifies the physical sequence and any parent - child relationship in the segments.
Mandatory Vs Optional Segments : When used in the IDOC type, each segment has an attribute that defines whether the segment is option or mandatory. Minimum/Maximum range for each segment: It defines the maximum and minimum number of timesa data record corresponding to a segment cn exist in an IDOC.
-Segments : A segment defines the format and structure of a data record. Segments are reusable componets. A segment consists of various fields that represent data in data record.
IDOC Record Types:
1. Control Record : The control record contains all of the control information about an IDOC, this information basically includes the IDOC number, sender and receiver information, and information such as the message type it represents and the IDOC type.
- there is only one control record per IDOC.
- The stucture of the control record is the same for all the IDOCs and is defined by SAP.
- The structure of the control record is defined by the data dictionary structure EDI_DC40. The control record is stored in the EDIDC table.
2. Data Record : Data records contain the application data. A data record has two sections
Administrative Section and a Data section.
- The Administrative section cotain the segment name, client, IDOC number, segment number, hierarchy level information.
- The Data section of a data record is a stram of 1000 bytes where the actual data resides.
- The data record is defined by the data dictionary structure EDI_DD40.
- Data records for IDOCs stored in the EDID4 table.
3. Status Record : Status records are attaced to an IDOC throughout the process as the IDOC achieves different milestones or encounters an error. At every milestone a statu code, date and time are assigned.
- Status codes 01 to 49 are reserved for OUtbound process, 50 and above are reserved for inbound processes.
IDOC TYPE IS AN INSTANCE OF IDOC
Message Type: Identifies what type of information transformed between logical systems or partners.Message type is not a local object type , it is transportable.
For different applicatons we have different MESSAGETYPE.
example:
APPLICATION MESSAGETYPE
MATERIAL MASTER MATMAS
VENDOR MASTER CREMAS
CUSTOMER MASTER DEBMAS
MATMAS01, MATMAS02, MATMAS03, MATMAS04, MATMAS05 are all MESSAGETYPES ... FOR NEW VERSIONS LIKE SAP 4.7EE, SAP ECC5.0....we have to use MATMAS05 message type. for older versions like SAP R/3 we have to use MATMAS01.
REWARD ME IF THIS IS HELPFUL

Issue: "No Authorization to send Idocs with message type Orders" - IDX5

Hi All,
I am working on a File to IDoc(Orders.Orders05) scenario. The sender is PI Server and the receiver is the SAP ISR system. A technical system has been created in PI SLD for the ISR system and a Business system is added to that. The logical system created in ISR system using Tcode BD54 is added to the business system in PI. A new RFC destination is created in PI system to connect to the ISR system.
On the ISR system Partner profile is created using TCode we20 with the same logical system name already created using Tcode BD54.
When sxi_monitor is executed on the PI system, It shows checked flag on the Inbound side and Red flag on the Outbound side. And when idx5 is executed, it shows the new Idoc number and when it is double clicked, it shows the Status Text as
"No Authorization to send IDocs with message type Orders".
All authorizations have been provided on the Sender side.
Please let me know if any authorization need to be provided on the ISR system or Is this an error on any settings.
Thanks in Advance.
Stalin S.

Hi,
Check this Thread which deals with the Authorization Issue
RFC Adapter
And also check this how to check whether u have sufficient authorization to send the Idocs or not
To test the Authorization check
Double click the RFC Destination that u have created in XI towards R/3 in SM59
Select UtilitiesTestAuthorization test
By this you can come to know whether your user is having the propper authorization or not
REgards
Seshagiri

IDOC vs Message type

Could some one explain me in detail what is an IDOC and what is a Message type with a simple example?
Appreciated.

Explaining in detail with a simple example!! Sounds interesting!!
Idoc type: Idoc is a package of data mainly used for communication between 2 systems, one of them being SAP and the other may or may not be SAP. Idoc type is the definition of the Idoc. It's in a way analogous to deep dictionary structure i.e, sturcture inside a structure. These structures in IDoc is called segments. For seeing a IDOc type you can go to WE30 while for segments you can go to WE31.
Message type: Message type determines what type of processing an idoc will undergo. You define message types in WE81 and link it with idocs in WE82.You can use same idoc with as many different message types, and then can process the data depending upon the message type (e.g. you want to process data depending upon company codes. that of course you can again do with a same msg type, but if you want to build security over that depending upon company codes, you will go for different msg types).
This is not as simple to explain in a few words. Get a book/document on ALE/EDI and start reading
If you need one, let me know your e-mail id.

Proforma Invoice - IDoc and message type

Hi,
The requirement is to send proforma invoice to legacy system upon creation. We use PI as middleware.
Is it possible to send to proforma invoice data using IDoc?
If IDoc then we have to use message control? Am i right?
What is the process code and what is the basic IDoc type/message type to be used for this?
Thanks for any help.
Cheers,
Srini

Hi Srinivasan
Basic type           INVOIC01 Invoice/Billing document
Message type                   INVOIC     Invoice / Billing document
Process code         SD09
Description          INVOIC: Invoice
Function module      IDOC_OUTPUT_INVOIC
best of lucks and Happy Diwali
Nandu

Idoc types & message types

hi friends, please can somebody post different kinds of Idoc types and message types used in sd , from sd's point of view. and also explain giving examples if you could. thanks
points will be awarded for sure . thanks
seema roy

Dear Seema,
concerning EDI concept in SD: the EDI concept is intended to realize the sales and distribution process completely automatically with the help of electronical documents. These documents are sent from one customer to another, are processed mostly on the background and give a possibility to realize the sales process extremely efficiently.
If MM-customer would like to purchase the goods then he creates the IDOC of type ORDERS and send it to SD-customer. On the SD-side the IDOC is processed via the function module IDOC_INPUT_ORDERS and creates the sales order. As confirmation the SD-side can send to MM-side the Order-Response IDOC (function IDOC_OUTPUT_ORDERS). The MM-customer can every thime send a change to the existiong order, then on SD side the ORDCHG IDOC will be processed. It can change the order like in VA02. The creation of the invoice can be made via IDOC of message type INVOIC (function IDOC_OUTPUT_INVOIC).
So, the process can be realized completely automatically between SD and MM partners with the help of IDOCs: ORDERS, ORDCHG, ORDRSP, INVOIC.
That's all concerning the SD-EDI.
Additional processes in SD, where EDI are used:
1) application of delivery schedules to the scheduling agreement: IDOC of type DELINS
2) creation of a delivery order to the scheduling agreement: IDOC of type DELORD
3) creation of external agent service delivery to scheduling agreement: IDOC of type EDLNOT
4) creation of credit advice / credit memo in the frames of self-billing: IDOCs of type GSVERF, SBWAP and for external invoice creation SBINV.
It is all processes which are realized in the SD module via EDI.
There is not so much Customizing for EDI. The most entries are required by EDI for the scheduling agreement processing (DELINS, EDLNOT, SBINV). The Customizing of these processes is located in the Customizing of scheduling agreements: SPRO => Sales and Distribution => Sales => Sales Documents => Scheduling agreements with delivery schedules => Control EDI Inbound processing.
General EDI Customizing in SD is available under: SPRO => Sales and Distribution => Electronic Data Interchange => EDI messages => ...
I hope this info helps.
Kind regards,
Akmal Vakhidov
Development Support SAP, Walldorf/Germany

RFC error "No authorization to send IDOCs with message type ..."

Hi all,
I have now tried just about everything I could think of, applied all the notes mentioned on this forum but still no luck. Can anyone please help ...
I have got a file to idoc scenario, the status in the sxmb_moni is successful, but the outbound processing logs an error. When I go to transaction SM58 I get an error for the user XIAFUSER with the message "No authorization to send IDOCs with message type WPUUMS".
I have tried giving this user SA_ALL access and still got the same error thus concluding that this is not an authorisation error.
Any suggestions?
Regards,
Liesel

Hi Liesel,
The RFC destination that you have put in IDoc communication channel must be present in your SAP XI system, transaction SM59 also.
Please check if the user id/Password that you have given has all the authorization.
Also check the User ID and passwrord in SM59 in R3 and see if a Remote Login is possible.
There is also some configuration by which the clients are allowed / blocked from receiving Idocs from XI. Basis guys can do it for you. Please approach your basis consultant. Hopefully that helps..
Regards,
Abhy Thomas

Error : No authorization to send IDocs with message type MATMAS

Hi All,
My scenario is FILE-XI-IDOC.
I am getting chequered flag in SXMB_MONI,but in that under outbound status I am getting red flag.
When I check in SM58 I am getting message as "No authorization to send IDocs with message type MATMAS".
Do I need to give any authorizations on XI side or on R/3 side?
If so, what is the authorization required?
I could not find the note :837595.

You use the IDoc Adapter in the Exchange Infrastructure and you try to use the IDocs to receive or send data. For these IDocs, an attempt is made to load the IDoc metadata from an R/3 reference system with an SAP NetWeaver Release lower than 6.20.
This occurs either at runtime, whereby the relevant messages run into 'System error' status, or when you use transaction IDX2 during manual loading of the metadata. In this case, the reference ystem is called by RFC and the logon user of the RFC destination does not have the necessary authorizations for determining the metadata.
Solution
In transaction PFCG, extend the role of the logon user by adding the following authorizations:
Authorization object S_RFC
 Field name RFC_TYPE value FUGR
 Field name RFC_NAME value EDIMEXT, SDTX
 Field name ACTVT value 16
Authorization object S_IDOCDEFT
 Field name ACTVT value 03
 Field name EDI_CIM value ' '
 Field name EDI_DOC value TXTRAW01
 Field name EDI_TCD value WE30
Authorization object S_CTS_ADMI
 Field name CTS_ADMFCT value TABL
Authorization object S_TABU_DIS
 Field name ACTVT value 03
 Field name DICBERCLS value
from the note mentioned above.
Regards
Bhavesh

IDOC of message type EUPEXR

hi all,
When I run RFFOEDI to gereate IDOCS, IDOCS of message type EUPEXR and PAYEXT are generated.
I need to pass a value in a field in the control record for the IDOC of message type EUPEXR but in FM : FI_EDI_EUPEXR_IDCREF01_OUT ( which is uesd to generate this IDOC ), control record is filled and before passing this control record to MASTER_IDOC_DISTRIBUTE, I could not find any exit to change its control record.
Please help.
Thanks and Regards
Gurpreet Singh

Hi Ferry,
System checks for the IDOC version and then calls the EXIT if the versions are different .Following is the code snippet that ensures the above thing in include LBD11F0T :
Change IDOC version if target <> current version.
IF F_EXCEPTION-MSGTY IS INITIAL
 AND ( F_IDOC_CONTROL-IDOCTP <> TARGET_IDOCTP
 OR F_IDOC_CONTROL-CIMTYP <> TARGET_CIMTYP ).
 PERFORM CHANGE_IDOC_VERSION TABLES T_IDOC_DATA
 USING TARGET_IDOCTP
 TARGET_CIMTYP
 CHANGING F_IDOC_CONTROL
 CHANGED_FLAG
 F_EXCEPTION.
ENDIF. "End of if subrc = 0
Have you tested it ? Pls suggest if I am wrong somewhere.
Thanks and Regards
Gurpreet Singh

Problem In IDOCS of Message Type ORDERS05

I am Trying to place Sales Order as soon as i recieve an idoc of Message Type ORDERS05. But It gives following error when it recieves the idoc of a Purchase Order.
VKORG, VTWEG, SPART cannot be determined for customer 0000003000, vend 0000005595.
I am not Getting This Problem.
Please Help.

Hi,
Please see the link below for some information.
ABAP Development
If you find the info useful please reward with points.
regards
Aveek

Using same Idoc type & Message type for 2 Interfaces

Similar Messages

Maybe you are looking for