IDOC processing inbound in receiver system , transaction WE57

Hello,
possibly a simple question for those who are familar with IDOC processing.
In transaction WE57 you can add function modules for processing IDOCs e.g. inbound IDOCs.
Now I see in our system that there are two function modules added to the same IDOC.
Example Basis type MATMAS03:
Function modules: IDOC_INPUT_MATMAS01 and IDOC_INPUT_MATMASMDM.
We want to add an individual mapping on receiver side (not on XI, because it has to be accessible to a user group on receiver side to change required field contents sometimes) for fields which are empty.
My idea is that we can add a func.module here in WE57 for this purpose. But what about the existing two FMs?
Will they be processed in a sequence so that we can add more FMs to the same IDOC type?
Or should I replace one of them with a Z_IDOC_INPUT_MATMASxxx by copying it and adding the required functionality?
Any help is appreciated!
Regards
Dirk

Hi Dirk,
Will they be processed in a sequence so that we can add more FMs to the same IDOC type?
I dont think ....
BTW you would get better response if you post the question in ABAP forum.
https://www.sdn.sap.com/irj/sdn/abap-forums
Regards,
Sumit

Similar Messages

PROCESS CODE IN RECEIVING SYSTEM

Dear gurus,
What is the process code in receving system in ALE.
should we create a new process code or select the process code from exists.
advise please.
Cheers,
R.Rajendran

process code will invoke related function module
you need the process code to determine which Function is used for creating/processing the IDoc.
Go to WE20 (Partner) and choose you inbound processing messages.
In the first tab you´´ll find the processing code.
Transaction: WE42 to define the processing code
Tcode: WE57 and BD51 to map the Function to this processing Code.
Process Codes will be linked to the inbound function module which in turn will read the data from the inbound idoc and post in the application document.Jus double click on the process code it will take you to the corresponding function module.

Issue:Creation of Extended iDOC data entries in receiving system.

Hi all,
I have extended standard IDOC MATMAS05 for classification view.I am receiving the data successfully on recewing side.And i have done coading in user exit to store data in database table inside
IDOC_INPUT_MATMAS01- function module.
When i execute the BD10 from sending sytem and view the idoc at receiving end from WE05 i can see the idoc but when i try to see the material i cant see the classification(extended) view in mm03.Rest of the views are created .When i execute the idoc from WE19 ,Classification(extended) view gets created.
Please guide me so that the CLASSIFICATION view get automatically created in receiving system without using WE19.
Thanks.

Yes i used this function module-
CALL FUNCTION 'BAPI_OBJCL_CREATE'
              EXPORTING
                objectkeynew            = objectkeynew1
                objecttablenew          = 'MARA'
                classnumnew             = wa_classnumnew1
                classtypenew            = z1sklart-klart              "classtypenew1
                status                  = '1'
STANDARDCLASS           =
CHANGENUMBER            =
                keydate                 = sy-datum
NO_DEFAULT_VALUES       = ' '
IMPORTING
CLASSIF_STATUS          =
              TABLES
ALLOCVALUESNUM          =
                allocvalueschar         = allocvalueschar2[]
ALLOCVALUESCURR         =
                return                  = return1
*WAIT UP TO 1 SECONDS.
            CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
             EXPORTING
               wait          = 'X'
IMPORTING
RETURN        =
Please explain me how to maintain the Views Status at MARA general info segment level.

Time out when seinding Idocs from XI to receiving system

Hi All,
we have implemented a file to Idoc scenario in our XI test environment.
When sending more than one file at a time (containing one record -> 1 Idoc after conversion) XI creates the Idocs but gets a time out when passing the Idocs to the receiving SAP 4.6C system. We find the messages blocked in transaction SM58 with the status message "Transaction recorded" and on the XI system short dumps are created with the time out error message.
Does anyone know this problem and can give us some hints how to resolve it ?
Thanks in advance,
Christiane

Christiane,
Check your partner profiles in the target R/3 system. Use Tcode WE20 and check the inbound parameters option to see if the radio button 'Process Immediately' is switched on. If yes, change this to 'Process by background program'.
This way, the IDOC will be created in your system with status 64. You can then use program RBDAPP01 in the R/3 system to post these IDOCs to application.
The reason I say this is, sometimes, posting applicaitons may take a long time thereby resulting in timeout. If this is not the actual reason, atleast this will lead you to the correct problem.
Try this and let me know what's happening.
KK

IDOC Process Stops Due To System Warning

Hello Friends,
Here is the ALE inbound scenario: We are setting up an order BOM interface using idoc BOMORD01. During the test, we found that the idoc has the error status 51 and this was due to a warning message issued by the system. In dialog mode (CS61 or CS62), we press enter to confirm the warning and thereby continue with the transaction. <b>The ALE process treats this API-warning as an error and stops.</b>
How can this be handled/resolved? Please help me out!
Thanks,
Sam

This turned out to be data problem. Of course, SAP's error message was not helpful.
We had to report this to SAP and they found the problem after some debugging.

IDOC Processing Inbound / Outbound

Hi Experts !!
As part of EDI Inbound processing our process is as follows.
1. EDI 850 files are created by EDI sub-system ( Sitting in differerent Environment ) and those file are trasfered to 'INBOX' folder on R/3 server using FTP file server.
2. A batch job ( for ex: EDI850_ORDERS ) executes every 15 minutes to process the files from 'INBOX' folder using the Custom ABAP program ZWRAP_RSEINB00. The program uses standard SAP inbound EDI file processing program 'RSEINB00' to process the file and try posting it into SAP. If the file is successfully posted then the file is deleted.
Here in this case client's requirement is once idoc file is processed archive the Idoc file from INBOX folder to 850_ARCHIVE folder on Application Server itself and NOT delete the file.
We have suggested that
Our Approach: As FTP is already in place, FTP the the files from EDI Substem to R/3 (INBOX) as well as on ARCHIVE folder even before IDOCs are processed so as to make sure Archival process is in place.
Client's Approach: Client suggests to Archival be handled from SAP and NOT through FTP.
Keeping performance and architecture in view kindly suggest which will the right approach.
Is it good to handle it from FTP / SAP !?
Or is there any other better approach to handle this!!? Please advice !!!!
Similarly Archival is required in case of Outbound as well for (810) !! suggestions appreciated !!
Thanks in advance,
Ramesh.
Edited by: Ramesh Kajuru on Aug 5, 2010 3:43 AM
Edited by: Ramesh Kajuru on Aug 5, 2010 5:45 AM
Edited by: Thomas Zloch on Aug 5, 2010 12:50 PM

Ramesh,
the client approch will be best and he will know which files are processed sucessfully.
if I remember correctly there is an FM which will do the same job as the program(I hope you can find with in the standard code).
call that FM in your Z program and read file 1 by 1 and once FM executed sucessfully move the file to archive directory.
IDOC_INBOUND_FROM_FILE. This is the FM I am refering. if still find the delete file code in this make a copy of it and remove that logic.
Regds,
Edited by: Suresh Reddy Avutu on Aug 5, 2010 2:26 PM

Same idoc to multiple EDI receiver system using rule

Dear Friends!
Good day! I am using desadv.delvry03 idoc and I want to send same idoc from same communication component to multiple receiver parties without mapping.
I have created first scenario successfully using idoc, when I create another scenario it gives me message like "Object already exist" . for that I have to use Service interface. I dont want to use service interface for this purpose. In my scenarios mapping is not even required. one idoc to and multiple receivers thats it.
Can you please guide me how to do the above requirement ?
your any help will be appreciated greatly
Thanking you
Regards
Dipen

Hi,
For this... U can create 1 sender agreent for that idoc if necesseary....otherwise we dont required IDOC sender Agreement.
Then Create 1 reciver determination in that u can mention the 2 recivers details...
same thing for interface determination also.
and finally create 2 reciver agreement and 2 reciver communication channels for 2 systems.
Let me know if you require any further information.
Thanks,
Sreenivas

Change IDOC Control Record in Receiver system

Hi Guys,
I want to change the inbound IDOC control record,is there any BADI or F.M available ?
My scenario : XI to SAP and its a custom application.
Regards,
Rajesh.

hi Rajesh,
You can refer this wiki link , this will help you out in your problem
https://wiki.sdn.sap.com/wiki/display/ABAP/IDOC+Steps
Regards
Saurabh Goel

How to process inbound idoc in R/3 with status 75 - idoc received via qRFC?

Hi gurus,
we are using EOIO for source to R/3, and all the idocs a received in r/3 with this status. But they can't be processed from BD87. How to process these?
Thanks,
Olian
Edited by: Olian Saludew on Sep 11, 2008 11:44 AM

Hi,
Idocs Works on tRFC Queues.
Check this Report to Process Inbound Idocs with Specified Status.
RBDAPP01
Regards
Seshagiri

Inbound Idoc processing issues - Partner Profiles - error status 56

Hello All,
I'm having a little difficulty posting an idoc coming from MDM. It's a CREMDM04 xml coming from an MDM system. It is getting mapped through PI and is being split into ADRMAS02 and CREMAS04 Idocs. The message is being passed through XI and being posted to the ECC system, but certain fields in the EDI_DC40 header table are not being populated correctly (i believe). I'm using nothing but standard mapping/material from the SAP Business Content for XI. After looking through the standard XSLTs i cannot find the field-to-field mapping where the fields below are being populated.
The RCVPOR value (SAP[SID]) is correct when i view it in SOAP Header, but does not appear in the remote system under the receiver port for the inbound idoc.
The RCVPRN value ([String Value]) is incorrect in the SOAP Header and does appear in the remote system under the receiver partner number for the inbound idoc. How is the RCVPRN value being populated?
SOAP Header in IDocOutbound tag
<SAP:RCVPOR>SAP[SID]</SAP:RCVPOR>
<SAP:RCVPRN>[String Value]</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
I've been trying to trace down the string value for the RCVPRN, but i cannot find it anywhere. Perhaps i'm just overlooking it?
When i set the proper values (port = SAP<SIDofECC> and partner number = <LSnameof ECC>) using WE19 in the remote system then the partner profile is found and i'm left with different error to please specify an address group.
Any help is very much appreciated! :-D

Hi Jason ,
Just check out if you have done the following steps most of us make minor mistake here ....... I think this would solve your problem
To Configure the IDOC SCENARIOS ,PROCEED AS FOLLOWS
STEP 1:ALE SETTINGS TO POST IDOC INTO SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Receiving System in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a) Select Create New button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client
d) Enter the RFC Destination created in XI towards R/3
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Inbound Parameters (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Message Type and Process Code.
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
do let me know if it helped
Edited by: Tom Jose on Feb 21, 2008 9:04 AM

Inbound Custom IDoc Processing

Hi,
I've created an Inbound Custom IDoc, Created the ABAP function module to post it to the application, configured workflow and IDoc processing. All my setup appears fine as I can create IDocs from our AS400 subsystem and trigger a successful posting via the IDoc test tool.
Having got this working I now want to automate the posting.
At present I create the IDoc's on our Legacy AS400 System and FTP them onto the SAP Application Server which runs on a Windows 2003 platform.
How do I get SAP to process each of my waiting Idoc's?
Any examples appreciated....

Hi
For CUSTOM IDOC inbound processing
Firstly attach your idoc to a process code.
In the process cod you can tell the system that the specified program should be triggered whenever an idoc of that type comes to the system.
Then you want to have a Z-function module for your idoc processing, if I understand correctly.The steps should be:
1. Create a z function module for idoc inbound posting (copy from a function module idoc_input_*).
2. Set Function Modules as Inbound: - Transaction BD51
3. Assign Function Modules to Logical Messages and Idoc types:- Transaction WE57
4. Create process codes : Transaction WE42, and link the z-function module.
5. Create partner profile: transaction WE20 and attach the message type and process code.
6. In the Z- function module, extract data from the idoc segments, do whatever processing you want to do, and then call BAPI_CREATE_SALES_ORDER_FROMDAT2.
Check out this sample Function Module on the inbound system
FUNCTION Z_IDOC_INPUT_EMPREP.
""Local interface:
*" IMPORTING
*"     VALUE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD
*"     VALUE(MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC
*" EXPORTING
*"     VALUE(WORKFLOW_RESULT) LIKE BDWFAP_PAR-RESULT
*"     VALUE(APPLICATION_VARIABLE) LIKE BDWFAP_PAR-APPL_VAR
*"     VALUE(IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK
*"     VALUE(CALL_TRANSACTION_DONE) LIKE BDWFAP_PAR-CALLTRANS
*" TABLES
*"      IDOC_CONTRL STRUCTURE EDIDC
*"      IDOC_DATA STRUCTURE EDIDD
*"      IDOC_STATUS STRUCTURE BDIDOCSTAT
*"      RETURN_VARIABLES STRUCTURE BDWFRETVAR
*"      SERIALIZATION_INFO STRUCTURE BDI_SER
*" EXCEPTIONS
*"      WRONG_FUNCTION_CALLED
Database Tables
TABLES: ZAK_EMPLIST.
Include programs
INCLUDE MBDCONWF.
Data Declarations
*--- Employee Header -IDOC
DATA: FS_EMPHDR_DATA LIKE Z1R_SEG1.
*--- Employee Details -IDOC
DATA: FS_EMPDET_DATA LIKE Z1R_SEG2.
*--- Employee Header - application data
DATA: FS_APP_EMPHDR LIKE ZAK_EMPLIST.
*--- Employee Details - application data
DATA: FS_APP_EMPDET LIKE ZAK_EMPLIST.
Program Logic
*---Initialize Work Flow Result
WORKFLOW_RESULT = C_WF_RESULT_OK.
LOOP AT IDOC_CONTRL.
*--- Check whether the correct message was passed to us
IF IDOC_CONTRL-MESTYP NE 'ZR_MSG'.
      RAISE WRONG_FUNCTION_CALLED.
ENDIF.
*--- Clear application buffers before reading a new record
CLEAR   FS_APP_EMPDET.
CLEAR   FS_APP_EMPHDR.
REFRESH FS_APP_EMPDET.
REFRESH FS_APP_EMPDET.
*--- Process all records and pass them on to application buffers
    LOOP AT IDOC_DATA WHERE DOCNUM EQ IDOC_CONTRL-DOCNUM.
      CASE IDOC_DATA-SEGNAM.
        WHEN 'Z1R_SEG1'.            " Employee Header
          FS_EMPHDR_DATA = IDOC_DATA-SDATA.
          MOVE-CORRESPONDING FS_EMPHDR_DATA TO FS_APP_EMPHDR.
        WHEN 'Z1R_SEG2'.            " Employee Details
          FS_EMPDET_DATA = IDOC_DATA-SDATA.
          MOVE-CORRESPONDING FS_EMPDET_DATA TO FS_APP_EMPDET.
      ENDCASE.
    ENDLOOP.
*--- If data is ok
SELECT * FROM ZAK_EMPLIST WHERE ENUMBER = FS_APP_EMPHDR.
    IF SY-SUBRC NE 0.
      INSERT INTO ZAK_EMPLIST VALUES FS_APP_EMPHDR.
      INSERT INTO ZAK_EMPLIST VALUES FS_APP_EMPDET.
    ELSE.
      UPDATE ZAK_EMPLIST FROM FS_APP_EMPHDR.
      UPDATE ZAK_EMPLIST FROM FS_APP_EMPDET.
    ENDIF.
ENDSELECT.
IF SY-SUBRC EQ 0.
*--- Populate Return variables for success
      RETURN_VARIABLES-WF_PARAM    = 'Processed_IDOCs'.
      RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
      RETURN_VARIABLES-WF_PARAM    = 'Appl_Objects'.
      RETURN_VARIABLES-DOC_NUMBER = FS_APP_EMPHDR-ENUMBER.
      APPEND RETURN_VARIABLES.
*--- Add Status Reocrds indicating success
      IDOC_STATUS-DOCNUM           = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS           = '53'.
      IDOC_STATUS-MSGTY            = 'I'.
      IDOC_STATUS-MSGID            = 'ZE'.
      IDOC_STATUS-MSGNO            = '006'.
      IDOC_STATUS-MSGV1            = FS_APP_EMPHDR-ENUMBER.
      APPEND IDOC_STATUS.
ELSE.
      WORKFLOW_RESULT              = C_WF_RESULT_ERROR.
      RETURN_VARIABLES-WF_PARAM    = 'Error IDOCs'.
      RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
      APPEND RETURN_VARIABLES.
*--- Add status record indicating failure in updating
      IDOC_STATUS-DOCNUM           = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS           = '51'.
      IDOC_STATUS-MSGTY            = 'E'.
      IDOC_STATUS-MSGID            = 'ZE'.
      IDOC_STATUS-MSGNO            = '007'.
      IDOC_STATUS-MSGV1            = FS_APP_EMPHDR-ENUMBER.
      APPEND IDOC_STATUS.
    ENDIF.
ENDLOOP.
ENDFUNCTION.
Good Luck and reward me for the same
Thanks
Ashok

Outbound IDOC not received at the receiver system.

Hi,
Im sending an IDOC from sap to a non-sap system. During this process, from sap system it is executing successfully without any erros and the status is also '03' .
The problem is that the other system is unable to receive the IDOC sent from SAP system.
The connection is like TCP/IP and the registered server program is given as 'PROGRID' in RFC destination.
I would like to know what would be the possible cases where this IDOC is not received at the receiver system.
The configuration is perfect as per my knowledge. Just want to confirm one thing 'do i need to include any message type such as "SYNCH".
Awaiting for your solutions.
Thanks
rohith

Hi,
If the IDOC is sent successfully from the sender system then the status of the IDOC will be '03' , no matter whether the receiver has received the IDOC or not.
As per your case,
Check the Partner Profile parameters , whether the basic and extended message types are used properly.
The message type Synchron (Sync) is generally needed in Inbound IDOC side. Check whether you have added SYNCH or not.
Hope this Helps.
Regards,
Abhinab Mishra.
Experience is the name everyone gives to their mistakes.

Idoc and message type not getting replicated in the receiver system

Hi
i have created a Z Idoc and didtributed the mode from system A ....I can see the distribution model in system B
However i cannot see the custom zidoc / message type in sys B.. Do i need to create the zidoc again in sys B

Hi Tarang,
at least ou need the required partner agreements and you should have a processing function for inbound IDoc. To implement this, the full definition of IDoc including Segment definition should be present in receiving system.
Just look at standard IDocs and do as they do.
Regards,
Clemens

Error while posting idoc in the receiving system.

i have processed idoc in the same system( sending and receiving idoc in the same system ) by creating a dummy logical sys and uploading a text file for customer details.The outbound processing is succesful and it shows a status message 3. But duriing the inbound processing it shows status as 51 with error as 'ENTER VALID VALUE'. but when testing using we19 it is posted sucessfully without any error..is there anything that i have to configure to process inbound idoc sucessfully?? can any suggest me the correct method for doing this.. suggestions please..
thanks
vidya sagar

Hi,
you need to make sure that in WE20 inbound processing parameters for you LS is maintained propperly. You need to give correct function module and enter whether IDoc should be processed immediately or IDocs should be collected and processed as batch. Also you may check whether the distribution model (BD64) is maintained correctly for the specific message type in the system for inbound processing.
Regards,
Kai

RPM_FIN02 - Receiver of IDoc is its own logical system

For one particular portfolio item, I run the RPM program RPM_FIN02.
This results in an IDoc creation.
Next, I checked the status of the IDoc (RPM > Base System Interfaces > SAP Financial and Controlling Integration > Data Distribution From SAP FI-CO to SAP xRPM > Check Inbound Processing).
This shows the status "29 - Receiver of IDoc is its own logical system".
As a result, the Internal Order costs (including the ones posted from cProjects) do not get pulled into RPM Financial Planning.
Please advise.
I do not have the technical understanding of this issue, and would therefore need a little more than the mere technical jargons and terms to be able to resolve this.
Thanks for understanding.

Hi,
Very briefly,
-Assuming your RPM system is independent of your ECC box. But RFC connected.
-RPM_FIN02 is for pulling in financial data onto RPM item from (object linked) Internal Order(IO)/PS Project(PSP).
-RPM_FIN02 do not recognize/goto cProjects for financials.
-cProjects can have its own account assigned IO/PSP
-cProjects Dashboard, (if all is well incl. evaluation) should display costs from assigned IO/PSP
-This cost does not reach RPM item
-Source of cProjects- if it is created within cProjects or from RPM Item, does not matter.
thanks,Mathavan

IDOC processing inbound in receiver system , transaction WE57

Similar Messages

Maybe you are looking for