Inbound logic for idoc

hello experts,
I have a query regarding inbound idoc.The input file is placed at application server and i need to read it and post it in SAP.My queries are:
1. In order to create an idoc using the file, we will use program RSEINB00 which will create idoc's with status 50 and then i need to link the correspiodning Function module in partner profile's inbound type and set it to automatic so that it gets posted into SAP? Is this correct? If yes, does it mean that there is no custom code needed for this case(Assuming that the FM linked in WE20 is standard)?
2. Can we dynamically process the file?Meaning, as soon as the file is placed at application server is there a way to invode the program RSEINB00 automatically
or should we run it manually ?
Please help with the process pls as it is slightly confusing.
Thanks,
Prem

yes your understanding is right and if you want the files are pulled from the server automatically then you run the report RSEINB00 in a job or you can create workflows for this.

Similar Messages

Inbound SOAP for IDoc : Register Service

Hi ,
We have a requirement where we need to post an Inbound IDoc in the R3 from a Web Service that is called from a 3rd party application, I found something in the Transaction
SALE->Basic Settings-> Inbound SOAP for IDoc : Register Service in R3 , the documentation says "You execute the report SRT_REGISTER_SERVICE to activate Inbound SOAP for IDocs." But I'm confused what needs to be done after that.
Can anyone throw some more light on the following issues :
a) where does the WSDL get stored for the IDoc,
b) how to register a particular IDoc as a web service such that it can be called from third party system.
Thanking all the experts in advance for their valuable time and help.
Regards,
Advait.

Hi Advait,
Did you get any further with this problem. I have the same issue and I don't know how to go further on this
Ron

Program logic for IDoc

hi everyone,
I am new to IDoc. Through some forums i came to know that we need to create
segment in we30
idoctype in we31
i understand the above two
msgtype in we80
attaching msgtype to idoctype in we81
i didnt understand how to do the above two, and also i want to know what to do next..like how to do the program
my mailID is [email protected](for any materials if u have)
Regards,
Venkata
Points will be rewarded to answers given
Message was edited by:
        venkata k

One very simple code:
==============================
*abap program to generate a customized idoc and send it to the target *system.
REPORT z_b8_ale .
TABLES : ekko,ekpo.
***Data Declaration for IDOC Begin
DATA : v_master_control LIKE edidc.
DATA : BEGIN OF int_idoc_data OCCURS 0.
        INCLUDE STRUCTURE edidd.
DATA : END OF int_idoc_data.
DATA : BEGIN OF int_comm_control OCCURS 0.
        INCLUDE STRUCTURE edidd.
DATA : END OF int_comm_control.
DATA : BEGIN OF itab OCCURS 10,
       lifnr LIKE ekko-lifnr,
       ekorg LIKE ekko-ekorg,
       ekgrp LIKE ekko-ekgrp,
       kdate LIKE ekko-kdate,
       ematn LIKE ekpo-ematn,
       ktmng LIKE ekpo-ktmng,
       meins LIKE ekpo-meins,
       netpr LIKE ekpo-netpr,
       werks LIKE ekpo-werks,
       peinh LIKE ekpo-peinh,
       END OF itab.
DATA : str LIKE edidd-sdata,
       sagrnum(10) TYPE c VALUE '5500000019'.
DATA:itab1 LIKE ekko OCCURS 0 WITH HEADER LINE,
     itab2 LIKE ekpo OCCURS 0 WITH HEADER LINE.
***Data Declaration for IDOC End
****FILL_MASTER_CONTROL
CLEAR v_master_control.
v_master_control-rcvpor = 'ZPORTB8'.
v_master_control-rcvprt = 'LS'.
v_master_control-rcvprn = 'D12503'.
v_master_control-mestyp = 'ZSCHB5'.
v_master_control-idoctp = 'ZSCHIDOC'.
****FILL_IDOC_DATA
CLEAR int_idoc_data.
REFRESH int_idoc_data.
int_idoc_data-segnam = 'ZSCHDLAGR'.
SELECT single * INTO itab1 from ekko WHERE ebeln = sagrnum.
SELECT single * INTO itab2 from ekpo WHERE ebeln = sagrnum.
MOVE itab1-lifnr TO str+0(10).
MOVE itab1-ekorg TO str+10(4).
MOVE itab1-ekgrp TO str+14(3).
MOVE itab1-kdate TO str+17(8).
MOVE itab2-ematn TO str+25(18).
MOVE itab2-ktmng TO str+43(16).
MOVE itab2-meins TO str+59(3).
MOVE itab2-netpr TO str+62(13).
MOVE itab2-werks TO str+74(5).
MOVE itab2-peinh TO str+80(5).
int_idoc_data-sdata = str.
APPEND int_idoc_data.
write : / str.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
     EXPORTING
          master_idoc_control            = v_master_control
     TABLES
          communication_idoc_control     = int_comm_control
          master_idoc_data               = int_idoc_data
     EXCEPTIONS
          error_in_idoc_control          = 1
          error_writing_idoc_status      = 2
          error_in_idoc_data             = 3
          sending_logical_system_unknown = 4
          OTHERS                         = 5.
COMMIT WORK.
WRITE : / 'IDOC Number created : ', int_comm_control-docnum.
Regards,
Gajendra.

Inbound file for IDOC processing

Hi SAP Gurus,
I want to create an IDOC by using INBOUND FILE option in WE19. Can anybody suggest, how the flat file will look like ?
FYI, my Idoc type is BBP_PCSTAT01 ( Procurement Card Statement).
Any idea ?
Thanks and Warm Regards.
Pras Durafe

This is an example of idoc with flat-file:
EDI_DC40 100000000000413988546B 2 INVOIC01 INVOIC MM E97A INVOICSNDPRN LIRS86092747 SAPITZ LS CLNTITZ100 20040210105203
E2EDK01005 100000000000413988500000000000001 USD INVO4139885
The first record indicate the header data; after this, for each segment type, the information about the segment.
If you send me your email address, I can send you a complete example file.
Gianluca

Inbound FM for IDOC OILBL_RECEIVEDETAIL01

Hi Gurus,
We are going to create the locations(O401), using IDOC OILBL_RECEIVEDETAIL01.
but I did not find any inbound FM and process code for the same.
Please help .
Thanks & Regards,
jitu188

Hi Sunil,
Looks like your Inbound side COnfig is still Incomplete as you are still tryint to Identify the Process Code. Pls go through below thread as it has more information regarding the enabling ALE for WorkCenter .
https://forums.sdn.sap.com/click.jspa?searchID=23909752&messageID=7198698
Pls let me know what you think.
Regards
Shital
Edited by: shital phadake on Mar 23, 2009 10:43 PM

Transaction SALE - Inbound SOAP for IDOC: Register Service

Hi,
Does anyone have some information on this feature in ECC 6.0?
Ron

Hi Advait,
Did you get any further with this problem. I have the same issue and I don't know how to go further on this
Ron

Inbound function module for IDoc type INFRECMASS01

Hello everybody,
What is the inbound function module for IDoc type INFRECMASS01?
I tried IDOC_INPUT_INFREC (as for IDoc INFREC01), but I got the following message (B1 044): Incorrect function module IDOC_INPUT_INFREC called up
Thanks in advance
Roland

The only difference between INFRECMASS01 and INFREC01 is that repitition of the same segments. However, the standard function module is hardcoded with IDOC type INFREC01, so if you want to use the MASS IDOC copy the standard one and put in the logic to loop around and process the info records one by one.
There is no standard funtion that can process mass idoc of the info record.
Regards,
Ravi
Note: Please mark the helpful answers

Need information on how to create Idoc Inbound Interfaces for Business Sys

Hi,
I'm losing it.
Can anyone point me to some documentation or an example of how to create inbound interfaces for Business Systems in PI 7.1.
Here's the scenario
I'm working on a B2B integration process which sends inbound idocs to an ECC 6.0 system.
I've created the Business System communication component but under the Inbound Interfaces it is blank.
I want to have MBGMCR.MGBMCR03 as an inbound interface.
But I forget how to get it there.
For Business components you can just add the inbound interface.
I've already defined the Business System in the SLD pointed it to the correct Tech System, imported the idoc definitions in the Enterprise Service Builder and set up IDX1, IDX2 to ensure the metadata exists in PI.
But for Business systems the hep says that it's got to come from the SLD.
Outbound/Inbound Interfaces
For each business system, the interfaces that are installed on the business system are also entered in the SLD. These interfaces are displayed in this frame. You cannot add any other interfaces.
I know I've done this before, but I can't remember how.
Cheers,
John

Hi John ,
Please have a look at the following links which might be of help to you
PI 7.1 IDocs interfaces act as operations
http://www.sdn.sap.com/irj/scn/weblogs;?blog=/pub/wlg/7933
/people/peter.gutsche/blog/2008/10/27/what146s-new-in-sap-netweaver-pi-71
There is a section in the following link on IDOC , have a look at the links in that section
https://wiki.sdn.sap.com/wiki/display/XI/ImportantBlogsand+Notes
Best Regards

Error : Pre Settings for IDoc inbound processing are missing error

Hi Experts,
There is a CRM job which executes LSMW and I am facing a strange problem during the IDOC posting the error "Pre Settings for IDoc inbound processing are missing error". Can anyone please tell me how to correct this error?
Thanks in advance.
Madhurima.

I'd start with the following document, with one modification. At step 12 after typing GEARAspiWDM press the Enter/Return key once prior to clicking OK. (Pressing Return adds a carriage return in the field and is important.)
[iTunes for Windows: "Registry settings" warning when opening iTunes|http://support.apple.com/kb/TS3299]

IDoc Inbound Processing for CREMDM & DEBMDM

Hi experts,
I'd like to gather some feedback from you regarding the topic ERP IDoc Inbound Processing for CREMDM & DEBMDM. As you all know, there's currently no option to directly process CREMDM/DEBMDM IDocs in ERP. Currently you have to use PI for splitting the CREMDM/DEBMDM message into its related ADRMAS and CREMAS/DEBMAS IDocs.
My areas of interest are:
1) How satisfied are you with the current situation? Does the split work? Are there issues or problems in the current message handling? What are the Pro's and Con's from your point of view?
2) What would be the requirements for a CREMDM/DEBMDM handler? What would you expect? Maybe you have implemented something similar on project basis and could post some feedback?
One painpoint I'd see with a CREMDM/DEBMDM inbound is that you'll lose the IDoc Monitoring capabilities. The message split allows a single record tracing in the IDoc Monitor (as there is a 1:1 relation between IDocs and records). This changes for the mass processing. The monitor would display only the status of the IDoc and you'd need some other monitoring capabilities to check the results on record level. What are your thoughts about that? Is the monitoring important? Would the application log be a feasible solution for that challenge?
Additional comments are welcome, of course.
Best regards
Michael
PS: @ Matt, please contact me by mail. thanks.

Hello ,
Here are some other pain areas regarding the message split :
1. Complicated monitoring proess & reprocessing error idocs : We have to monitor ADRMAS & CREMAS or ADRMAS & DEBMAS during inbound processing. Also we could not find any best practices to reprocess error idocs. E.g. If ADRMAS fails & CREMAS succeeds what is the impact . Also the impact if it is reveresed. We know for sure that if CREMAS fails , vendor will not be created / updated. But we could not find specific pointers for ADRMAS failures.
2. It is a tedious process to link CREMAS with corresponding ADRMAS idoc specially when SAP maintains internal number range for vendors.
3 . The process is complicated if you are managing customer or vendor contact information with contact address . We could succesfully implement the integration but it took us a while to reach end-point.
4. Splitting really does not seem to support if ERP maintains internal number range.
5. Another major issue we observed is , if ADRMAS is under process & corresponding DEBMAS or CREMAS is posted , it fails raising the message that Account is locked. Default serialization does work in ERP system . But overlap of few microseconds also cause this error.
Hope this helps !!
Please let me know if you need any other specific details since we have used MDM - ECC integration using PI to its maximum extent .
Regards
Yogesh

Inbound for idoc INVOIC

Hi
Can anyone tell me, what inbound function module should be given for Idoc type INVOIC.
Thanks

Hi Niranjana,
Check the function modules IDOC_INPUT_INVOIC_FI,IDOC_INPUT_INVOIC_MRM and IDOC_INPUT_INVOIC_MM
Regards,
Soumya.

Segment for WBS element in Inbound Sales Order Idoc

Hi gurus,
I am trying to create an inbound idoc for sales order ' VA01'. I need to populate WBS element in the item level under Account Assignment Tab. I am using ORDERS05 basic type. Please help to find which segment to use for WBS element. Waiting for your reply. Please help.
Regards,
Satyajit

Hello,
        As far as I know, there is no Segment / Field definition in ORDERS05 for WBS Element as it is not mandatory information to be filled in order for the Sales Order to be Complete. So, you need to create an Extension of the IDoc Type ORDERS05. For your requirement, here is the Approach I have.
1. Create an extension for IDoc Type ORDERS05 to ZORDER05 with a Custom Segment Z1EDP01 in which you'll have the Custom Field Name VBAP-PS_PSP_PNR which is the WBS Element field in VBAP Table.
2. Now, use the Customer Exit EXIT_SAPLVEDA_001 in the Enhancement VEDA0001 in which you can actually populate the Field WBS Element that would be already available in the Inbound IDoc to store it in a Work Area. As you are aware, you'll need to create a Project in CMOD for the same.
3. Export the same to some MEMORY ID 'XXX'.
4. Come back to the Selection Program for ORDER05 which is IDOC_INPUT_ORDERS in which you'll find the below CASE Statement.
    CASE xaprau.
          WHEN ' '.
            PERFORM call_va01_new_orders USING ok.
          WHEN 'Q'.
Aufruf Transaktion Auftragerfassung VA01 mit Bezug auf Angebot
call transaction Order Entry VA01 with refer to quote number.
            PERFORM call_va01_new_orders_angbt USING ok.
          WHEN 'C'.
Aufruf Transaktion Auftragerfassung VA01 mit Bezug auf Kontrakt
call transaction Order Entry VA01 with refer to contract number
            PERFORM call_va01_new_orders_contk USING ok.
          WHEN 'L'.
5. Now, since our Standard Order Type (VBAK-VBTYP) is 'C',
    we'll have to choose the Subroutine for the 'C' Option.
6. In this Subroutine, there is another Subroutine va01_dynpro_kopf_kaufmann_kde2 which is for populating Custom Dynpro Fields for the Sales Order. So, we need to choose the same Subroutine inside which we have to Create an Enhancement Implementation.
7. In this Enhancement Implementation (Implicit), we have to IMPORT the value of the WBS Element which was exported in the Customer Exit.
8. Check if it is initial. If it is not, then Call the Perform as below.
     IF NOT WA_Z1EDP01 IS INITIAL. "Checking if the Segment
                                                       " is Empty
   PERFORM DYNPRO_SETZEN USING 'COBL-PS_POSID' WA_Z1EDP01-ZZWBSELEMENT.
ENDIF.
9. Since the Sales Orders are posting using BDC here, by calling the above Subroutine DYNPRO_xxx, we are appending our Custom Segment / Field value to the BDC_DATA table.
10. In Step 8, I've given the Notation for Work Area. It will also be applicable when there are multiple Line Items. All you have to do is to EXPORT an Internal Table instead of Work Area and use the same here for each Line Item.
11. I've given you above procedure because I've worked on similar requirement in which I had to populate the Special Processing Indicator instead of WBS Element.
Hope it would be helpful for you.
Thanks and Regards,
Venkat Phani Prasad Konduri

User exit for IDOC inbound CREMAS

Hi experts,
I want to find a USER EXIT to change the value for vendor inbound idoc of message type CREMAS when create a new vendor or change a existing vendor. EXIT_SAPLKD02_001 is a function module can be enhanced but it cannot be called when I debug in WE19. The segment of IDOC is not extended by customazing field.
Can anyone tell me what user exit is for IDOC I can use to change the data for vendor when inbound idoc receive?

Hi panzhijun,
please check this link
http://forums.sdn.sap.com/thread.jspa?threadID=1659323
An Expert V.V.Reddy is exactly discussing about your issue on extending the FM in a Include: LKD02F01,
just have a look on this and go throw completely so u may get some solutions .
This is how somewhat i can help you , If i get any further details will let u know .
BR,
Lakshmi Rajkumar.

How to write the logic for extending Idocs...

Hi,
      Can anybody pls explain how to write the logic for extending IDOCs with an example...
      Good suggestions can be appreciated..
Regards,
Ram

Hi Ram,
Generally the IDoc user exit is called at the following places:
1) When the control record is read.
2) After each and every segment in the data record
3) At the end of the data segment processing.
The IDoc user exit interface generally imports IDOC_DATA (data record internal table) table. Now the data records in the internal table should appear in the same order as maintained while defining IDoc structure (WE30 transaction). For SAP standard segment SAP code will take care of this. For extended segment you will have to take care of this aspect by appending the Z-segment in the IDOC_DATA table.
You can do this by:
         looping at IDOC_DATA table:
             - Do a case-endcase fo IDOC_DATA-SEGNAM (This stores the segment
               structure as per the hierarchy).
             - Within the case for "Z-segment" you can write the logic for appending
               the Z-segment to IDOC_DATA-SDATA.
Hope this gives some clue.
Regards,
Gajendra.

Delivery date issue in the ASn inbound process via IDOC

HI
we want to start with ASN and we ´re already receiving IDOC´s
DESADV Delvry03
we are using Fm /SPE/IDOC_INPUT_DESADV1 and we have tried IDOC_INPUT_DESADV1 but teh reesult was the same.
The segment E1EDT13 Qualifier 007/009/006 exist and we are able to create a inbound delivery. The problem we have is that we are not able to calculate the delivery date in the inbound delivery.
The idea was that the vendors sends us the GI date (Qualifier 007) and our SAP calculates based on the plannend delivery time in the SA/PO the expected GR date 8what we see in MD04). But at the moment we only the creation date as delivery date.
what do we miss?
thanks for the help
regards
Alex

Hi,
Firstly, for DESADV processing delivery date field (LFDAT) is taken from qualifier '007' while goods issue is from '006'.
As far as I understood you would like to get delivery date based on data from given delivery schedules. But note that inbound delivery items are not related specifically to delivery schedules. Instead, those are referenced to purchasing document items only. Therefore it is not exactly specified what delivery date should be selected for which inbound delivery.
Alternative could be to perform scheduling for inbound deliveries based on route transit times etc.But in standard inbound delivery types are not available for SD scheduling and thus it is not directly available.
If you need to get such functionality, you would need to use one of the DESADV processing u-exits available and include your own logic for lfdat calculations.
Regards,
Dominik Modrzejewski

Inbound logic for idoc

Similar Messages

Maybe you are looking for