Exact inbound Idoc or RFC for BP based on ROLE/Customer/Vendor ?

Hi ,
I need a inbound IDOC or RFC for Business partner in BP transaction posting based on Customer master or vendor master Role ...

Hi Frederic,
I need to post data in to BP transaction(customer master data and vendor master) role using BODS via IDOC. Required IDOC's for posting.

Similar Messages

Inbound Idoc function module for Cycle count with msg type WVINVE

Can any one tell me which is the standard function Module which processes Cycle count for message type WVINVE.
My requirement is to setup Inbound Idoc for cycle processing with message type WVINVE.

Hi Mukesh,
Inbound FM is IDOC_INPUT_STORE_INVENTORY , and Process code is WVIN.
Yoou can check this in Tcode WE42 for process code WVIN.
Regards
Srikanth M

Inbound Idoc for material document cancellation

Hello,
Could you update me whether there is any Inbound Idoc type available for material document cancellation (like t.code MBST). I found message type MGBMCR, but it's only allowing me to create the material document like GRs but not cancellations.
/Mallik

To my knowledge, there is no such IDoc. Cancellation is an exceptional situation and should be treated as such. If one needs an IDoc interface for cancellations, I'd have to say there is something very wrong with the business process.

Using Inbound IDOC from Java system creation of Outbound delivery

Dear Experts,
The scenario we are having is really very interesting. Hopefully its a good learning for me and also for others also.
The scenario is,
After sales order creation the details will be sent to one Non SAP system (Java) for performing some tasks related to forwarding agent decision, shipping date and etc. Once the details are finalized in that Java system then, the details needs to be transferred to SAP as "Inbound IDOC" process. For this proposed to use the SAP Jco middle ware.
Once the details transfered from Java system to SAP then, the outbound IDOC needs to get generated automatically. Assuming the stock for that sales order line item is available. Also one more complexity is, our client is using custom transaction (ZVl10C) for delivery creation.
Now Query is,
1. Which IDOC, message type and Functional module needs to be used for creating the delivery automatically..??
2. As per assumption, stock of that sales order line item should be available. Due to some business reason the stock was removed during inbound IDOC transfer then, what will happen to the IDOC..?. How to avoid this situation..??
3. As we told we are re going to use SAP Jco b/w SAP & Java system. In this case, how the data will get transfered from Java system to SAP..?
Thanks in advance for the replies I am going to get
Regards,
VEL

Thanks for the feedback. This question is resolved

Outbound delivery creation with inbound IDOC transfer from Java system

Dear Experts,
       The scenario we are having is really very interesting. Hopefully its a good learning for me and also for others also.
The scenario is,
               After sales order creation the details will be sent to one Non SAP system (Java) for performing some tasks related to forwarding agent decision, shipping date and etc. Once the details are finalized in that Java system then, the details needs to be transferred to SAP as "Inbound IDOC" process. For this proposed to use the SAP Jco middle ware.
             Once the details transfered from Java system to SAP then, the outbound IDOC needs to get generated automatically. Assuming the stock for that sales order line item is available. Also one more complexity is, our client is using custom transaction (ZVl10C) for delivery creation.
Now Query is,
               1. Which IDOC, message type and Functional module needs to be used for creating the delivery automatically..??
               2. As per assumption, stock of that sales order line item should be available. Due to some business reason the stock was removed during inbound IDOC transfer then, what will happen to the IDOC..?. How to avoid this situation..??
               3. As we told we are re going to use SAP Jco b/w SAP & Java system. In this case, how the data will get transfered from Java system to SAP..?
Thanks in advance for the replies I am going to get
Regards,
VEL

Didn't get any feedback from experts for long time. So we are closing the question

INBOUND IDOC issue

Hi,
I'm facing the following problem:
A program reads a file from a directory in the unix server itself and populates an IDoc. No BDC is involved.The file contains all the data required to populate the IDoc like control record, data records etc. But when the IDoc is posted, it fails giving the message " <b>Receiver port in the control record is invalid</b> ". But when I try to reprocess the IDoc through WE19 without changing anything, I'm able to process it successfully by giving the <b>Inbound Function Module</b> corresponding to the process code.This is not happening in the case of <b>Standard Inbound</b>. I'm using a file port with ALE services but not EDI.All the other configurations are maintained.
Please suggest a solution.
Thanks,
Raj.

Hi Rajgopal,
for an inbound idoc no need for port configuration.Please see whether u have done all the configurations correctly.Also if this is inbound that means u r updating to SAP , so already data will be available in control record and data record.So please check the sender information and the receiver information.check the port the sender using.
For a custom function module,custom message type,custom basictype,the below configurations r generally done.
1>we81
2>we31
3>we30
4>bd51
5>we57
6>we42
7>we20
In we20 u have give u r zmessagetype in the inbound parameters and also u r custom process code.
Regards,
Nagaraj

Creating Inbound IDoc Using LSMW

How to create the inbound IDoc using LSMWu2026
For example
Input is Flat filesu2026.
I created custom IDoc with header and items
Structure looks
Header 1
Item 1
Item 2
Header 2
Item 3
Item 4
Header 3
Item 4
Item 5
u2026u2026.
u2026u2026.
u2026u2026..
Do I need to create different flat files (item level & Header level) as input while creating IDoc using LSMW ??
Can some one guide me on thisu2026with best way to create IDoc using LSMW with flat fileu2026.
Ramesh

can you please help me ... how input file to LSMS looks ..Sample file is helpful...
My Structure
E1EDK01    < Header Data
E1EDK14    < Header Data
E1EDK14    < Header Data
E1J3K03     < Header Data
E1EDK05    < Header Data
E1EDK05    < Header Data
E1EDKA1    < Header Data
E1EDKA1    < Header Data
E1J3P01      < Header Data
     E1J3AIM     < Item Data
     E1EDP20     < Item Data
E1J3P01      < Header Data
     E1J3AIM       < Item Data
     E1EDP20      < Item Data
Header had 3 segement E1EDK14   E1EDK05 & E1EDKA1 repeating twice.... i am facing prolem with this
What Structure format i used for above segement in LSMW and what file format i should use..for input to LSMW...
Edited by: Ramesh on Mar 25, 2009 1:26 AM
Edited by: Ramesh on Mar 25, 2009 1:41 AM
Edited by: Ramesh on Mar 25, 2009 1:44 AM

Finding a IDOC or RFC in SAPHR

Hi,
Can you suggest me finding standard IDOC or RFC :
Typically we have to feed some input fields to SAP HR system for employee performance purpose. We are about to find standard IDOC or RFC for feed to HRP SAPR/3.
Input is : CSV file.
File size expected to be less than 10,000 rows and typically less than 5,000 rows
SAPR/3 would use either RFC or IDOC to process input file
--> Still we need to find standard IDOC or RFC for feed this input.if we do not find IDOC or RFC then what is other methodology to feed this data into HRPSAPR/3? and how do we find standard IDOC or RFC for HR employee details?
Middleware we are using XI.
Thanks in Advance.
PILeran

hi
follow the link for list of idoc tyoes
http://www.sapmaterial.com/messagetypes_Assignment_to_IDOCtypes.html
regards
ravish
<b>plz dont forget to reward points if helpful</b>

Step-by step procedure for INBOUND IDOC (VENDOR CREATE / CHANGE)

Hi ,
Can any body provide me the step-by-step procedure for Inbound IDOCS.
As i'm new to this i need the the clarification between Inbound & outbound idocs.
How can we differentiate both?
where to define outbound & where to define Inbound?
( If possible Please explain me the procedure for Vendor Create through INBOUND IDOCS )
Thanks in advance..

Hi,
Ale Technology is SAPu2019s technology to support distributed yet integrated processes across several SAP systems.
Outbound Process:
ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
Inbound Process:
The inbound process receives an IDoc and creates a document in the system.
1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
Over view of IDocs:
IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDocu2019s definition and IDoc Data is an instance of the IDoc Type.
IDoc Types:
IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
An IDoc is an instance of an IDoc Type and consists of three types of records.
i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
Message in IDoc Type:
A Message represents a specific type of document transmitted between two partners.
Outbound Process in IDocs:
Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
The Customer Model:
A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
Message control:
Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
Change Pointers:
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
IDoc Structure:
A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
Selection Program:
Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programu2019s design depends on the triggering mechanism used in the process.
Filter Objects;
Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
Port Definition:
A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
RFC Destination:
The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
Partner Profile:
A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocu2019s packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
Service Programs and Configuration Tables:
The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
Process flow for Distributing Transactional Data:
Transactional data is distributed using two techniques: with Message control and without message control.
Process flow for Distributing Master Data:
Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.
Triggering the Outbound Process via Stand-Alone Programs:
Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.
The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.
Triggering the Outbound Process via Change Pointers:
The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.
A standard program, RBDMIDOC, is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.
Processing in the Application Layer:
The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.
Processing in the ALE Interface Layer:
Processing in the ALE Layer consists of the following steps:
u2022 Receiver Determination: The determination of the receiver is done through Customer Distribution Model.
u2022 IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.
u2022 Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.
u2022 Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.
u2022 Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.
u2022 Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.
u2022 Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).
u2022 Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc u2013 Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch u2013 ALE Service).
u2022 IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).
Processing in the Communication Layer:
To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.
Inbound Process in IDocs:
An inbound process used IDoc structure, posting programs, filter objects, conversion rules, a partner profile, service programs, and configuration tables to post an application document from an IDoc.
Posting Program:
Posting programs, which are implemented as function modules, read data from an IDoc and create an application document from it. A posting program exists for each message. Each posting program is assigned a process code. A process code can point to a function module or a work flow. In the standard program process codes always point to a function module.
Ex. The posting program for message type MATMAS is IDOC_INPUT_MATMAS which has a process code MATM.
Workflow:
A workflow represents a sequence of customized steps to be carried out for a process. The workflow management system is used to model the sequence, identify information required to carry out the steps and identify the person responsible for the dialog steps.
Partner Profile;
A partner profile specifies the components used in an inbound process (partner number, message type, and process code), the mode in which IDocs are processed (batch versus immediate), and the person to be notified in case of errors.
Process flow for the Inbound process via a Function Module:
In this process, IDocs are received from another system and passed to the posting function module directly.
1. Processing in the communication Layer:
The IDOC_INBOUND_ASYCHRONOUS program, triggered as a result of an RFC from the sending system, acts as the entry point for all inbound ALE processes. The IDoc to be processed is passed as an input parameter. Control is transferred to the ALE/EDI layer.
2. Processing in the ALE/EDI Interface Layer:
u2022 Basic integrity check: A basic integrity check is performed on the control record.
u2022 Segment Filtering and conversion: Filtering out unwanted segments and carry out any required conversion of field values.
u2022 Creation of Application IDoc: The application IDoc is created and stored in the database and a syntax check is performed. If there are errors it gets status code of 60 (Error during Syntax check of IDoc u2013 Inbound). At this point a tangible IDoc, which can be monitored via one of the monitoring transactions, is created and the IDoc gets status code 50 (IDoc Added).
u2022 IDoc Marked ready for Dispatch: IDoc gets the status code 64 (IDoc ready to be passed to application).
u2022 IDoc is passed to the posting program: The partner profile table is read. If the value of the Processing field is set to Process Immediately, the IDoc is passed to the posting program immediately using the program RBDAPP01.
3. Processing in the Posting Module:
The process code in the partner profile points to a posting module for the specific message in the IDoc. The posting program implemented as a function module either calls a standard SAP transaction by using the Call Transaction command for posting the document or invokes a direct input function module.
The results of execution are passed back via the function moduleu2019s output parameters. If the posting is successful IDoc gets the status code 53 (Application Document Posted) or it gets status code 51 (Error: Application Document Not Posted).

Creating Delivery based on the Inbound IDOC received.

Hi all,
I have a requirement where in, Outbound Delivery for Sales order is to be created based on the inbound IDOC received from a third party. The standard idoc type DELIVERY03, requires the Delivery Number for updating the order but it cannot create a delivery number.
Can any one suggest which IDOC type can be used for this or if there is any alternative solution?

Hi,
You can use FM IDOC_INBOUND_WRITE_TO_DB to create an inbound IDoc.
CALL FUNCTION 'IDOC_INBOUND_WRITE_TO_DB'
    EXPORTING
      PI_STATUS_MESSAGE       = I_EDIDS
    IMPORTING
      PE_IDOC_NUMBER          = DOCNUM
      PE_STATE_OF_PROCESSING = STPROC
      PE_INBOUND_PROCESS_DATA = I_TEDE2
    TABLES
      T_DATA_RECORDS          = I_EDIDD
    CHANGING
      PC_CONTROL_RECORD       = I_EDIDC
    EXCEPTIONS
      IDOC_NOT_SAVED          = 1
      OTHERS                  = 2.
Check the following link:
http://www.sapbrain.com/TUTORIALS/TECHNICAL/IDOC_tutorial.html
<b>Reward points</b>
Regards

What is the standard inbound idoc for substation management?

Hello Experts,
Can anybody help me to find out the standard inbound idoc for substation management?
The following field are requied to be filled in idoc.
1)Power_Produced(STAGR)
2) Reduction_Power_Consumed(STAGR)
3)Ancillary_Power_Consumed (STAGR)
4)Unit (MEINB)
5) UOM and Date (BUDAT)
If possible please tell me the standard BAPI for these fileds.
Thanks in advance for your help.
Thanks and Regards,
Suresh.

Hi Debo,
What is your exact requirement?
Are you trying to find the standard configurations available for a webdynpro application? then, use t-code SE15 and open the application name and use the tree structure to find out the available configurations under WD application.
sample:
Regards,
Rama

Procedure for Mapping two types of Idocs from RFC function Module

Hi
My Scenario is RFC -- XI -- IDOC
Here i have 2 custom Idocs
First IDOC for Creation
second is for Deletion/Changing
Based on the condition from RFC it should trigger either one of the IDOC above.
Please provide me the procedure to do in IR and ID..
Regards,
Yeswanth.

YeswanthRaj:
I found your conflicted statements
The following statement you say you just have one receiver, to receive two IDOCs
But i have only one receiver where the 2 IDOcs needs to be send based on the condition..
The following statements showing that you have more than one receiver,
the condition editor for receiver determination usually used for multiple receivers based on XPATH or Context Object condition
It is mapped based on the condition that is given in Receiver Determination and i has two interface Determinations.
It seems that the first scenario is your situation.
If your answer is yes, and your source interface is just one,and target interface is two (two IDOC), then this should be typical
muti-mapping scenario, and the propose I gave to you should fit
Regards.
Liang

Partner profile for INBOUND IDOC

Dear experts,
Need your help to define partner profile for inbound idoc to R/3 system. There is a third party (Non SAP) based application from which idocs need to be sent to the R/3 system. There is no need to send an outbound idoc from the R/3 system. Can some one please suggest what are the steps to be taken to b configure the partner profile in the R/3 system for the inbound idoc?
Thanks,
Priyanka

Hi
This is not the right location to post this question.
You got to post this query in Data transfers section of SDN ABAP Development forums
Now regarding your question,
You need to create a Logical System with the help of the transaction SALE.
Assign the created LS to the client with the help of same transaction
Go to WE20 and create the partner with the same Logical System name
Now..as you are recieving the Inbound Idoc from external Non-SAP System, you need to maintain the message type in the Inbound Parameters by clicking on ADD Icon over there.
Before doing the above step, you got to create the connection between SAP and Non-SAP System.
Use transaction SM59 to do this. Type of connection would be R/3 I guess
Thanks
Hope it helps.

How to get Get IDOC Number for Inbound IDOCS

Hi,
I am using the FM -- IDOC_INPUT_HRMD for creating Inbound IDOCS.
I populate the values for Control Record and Data Record and the IDOC is posted successfully and i get the status 53 in the status Table.
But the problem is the field for IDOC number(DOCNUM in IDOC_STATUS Table of the FM ) is empty.
How can i get the DOCNUM for the IDOC posted as a result of this FM ?
regards,
Siddhartha

Hi Siddhartha,
I think you cannot call IDOC_INPUT_HRMD fm directly from the external program as this fm only handles the application logic part and not the idoc number generation and save part.
So I think you have to call IDOC_INBOUND_SINGLE from your external program and then get the IDOC number.
Then if you need the status records then you need to call another fm and feed IDOC number that you have got from IDOC_INBOUND_SINGLE (there is one IDOC_READ_COMPLETELY but it is not a remote enabled fm)
<b>OK, I just found one RFC enabled fm which you can use,
<b>EDI_DOCUMENT_READ_ALL_STATUS</b></b>
Hope this helps..
Sri
Message was edited by: Srikanth Pinnamaneni

How to trigger change documents based on inbound-idoc?

Hi experts,
Currently I'm working in on a project where I have to create an interface based on IDOCS. This is an interface for two SAP-HR systems.
If there are made changes in the dialog (gui) by a user, there will be created a change document, which can be displayed by report RPUAUD00. For the inbound-interface based on idocs it's important that there will also be created a change document in the system based on this idoc. We have tested this, but no change document is created.
Can anybody help me to solve this problem: "How to create a change document based on the inbound-idoc?"
Thanks in advance.
With kind regards,
Roy

Thanks for responding. First, I like the idea of defining an event, but I'm still stuck with how to trigger it. I looked at dynamically registering events, and maybe doing something where a click on the graph control registers an event for key presses on the vi. I'd still have to figure out out to terminate the key press event. Unfortunately, (actually it's a feature I like..) there are a number of different ways to complete typing in a scale change. I routinely use ctr-enter (habit from working on a laptop), though enter works fine, and clicking somewhere else is probably the most common method. I am not that familar with User Defined Events, so I may be overlooking something obvious here.
The graphs are a Bode Plot, with a seperate graph for RPM vs Phase Lag, and RPM vs Magnitude. I want them to always be plotted on the same x-axis. The plot is generated when the user doubleclicks on a dataset. After that, it's just the user looking at it. They can change the axis without any new data being generated.
Thanks,
Chris

Exact inbound Idoc or RFC for BP based on ROLE/Customer/Vendor ?

Similar Messages

Maybe you are looking for