Generate inbound IDOC

Hi All,
The scenario is like... One system say S1 is sending an IDOC to second system say S2.
Now is this idoc is coming through a middle ware AMTRIX. In S2 the IDOC is coming as file and saved in UNIX path (al11).
From last 2 days IDOC is not getting generated from that file.
I guess there must be some standard program which is generating IDOC from that file which might have been running every day. We also don't know the batch job name.
Can you please tell me the name of the Standard program. Or is there ALE configuration is done ???
Any kind of input will valuable.
Thanks in advance
Satyam

Hi,
You must configure a fileport(WE21) to pick the file from the server location
Then configure the partner profile for the fileport in WE20 for the inbound process code.
the inbound process code will internally trigger the processing FM and generate the corresponding inbound IDOC.
Hence check the port and partner profile configuration and then check the test idoc tool in WE19
Regards
Shiva

Similar Messages

Regarding getting data from excel file and need to generate inbound idoc

Hi guys,
Please can u give some example how to get excel file data and need to generate the inbound idoc my questation ? Is it possible to generate inbound idoc with the same logical system ( it seems to be not possible using same logic to generate idoc ) can u suggest me any posssibule way to generate idoc.) if possible give me some example.
Regardng
anil
Edited by: anil kumar on Aug 8, 2008 1:35 PM

If you want someone to do your work, please have the courtesy to provide payment.
http://www.rentacoder.com

Need Code to generate Inbound Idocs

Hi friends
i have a flat file consists of delivery confirmation data
by using this i need to generate inbound idocs
i filled all the segments in idoc type /afs/delvry03 and message type whscon
can any one have the code to generate inbound idocs
please remember that here i am not using XI
thanks
Anil

Hi this is for Stand alone Programs, I hope it is useful to you.
Program Flow
The program logic contains the following blocks:
1. Provide a selection screen to allow a user to specify the various objects for which IDocs are to be generated.
2. Determine the key of the application document from the object specified in step 1.
3. Select application data from the database using the object key identified in step 2.
4. Populate control record information.
5. Populate an internal table of type EDIDD with data records for the various segments.
6. Call the ALE service layer (MASTER_IDOC_DISTRIBUTE) to create the IDocs in the database.
7. Commit work.
The program in Listing 32-2 generates the monthly report IDoc ZMREPT01, which illustrates a stand-alone outbound process.
Listing 32-2
REPORT ZARNEDI1 MESSAGE-ID ZE.
Parameters
object key (Social security number for the employee)
PARAMETERS: P_SSN LIKE ZEMPDETAIL-SSN.
message type
PARAMETERS: P_MESTYP LIKE EDMSG-MSGTYP OBLIGATORY.
destination system
PARAMETERS: P_LOGSYS LIKE TBDLST-LOGSYS.
Constants
DATA:
    segment names
        C_HEADER_SEGMENT           LIKE EDIDD-SEGNAM VALUE 'Z1EMHDR',
        C_WEEKLY_DETAILS_SEGMENT   LIKE EDIDD-SEGNAM VALUE 'Z1WKDET',
        C_CLIENT_DETAILS_SEGMENT   LIKE EDIDD-SEGNAM VALUE 'Z1CLDET',
        C_SUMMARY_SEGMENT          LIKE EDIDD-SEGNAM VALUE 'Z1SUMRY',
    idoc type
        C_MONTHLY_REPORT_IDOC_TYPE LIKE EDIDC-IDOCTP VALUE 'ZMREPT01'.
Data declarations
idoc control record
data: control_record_out like edidc.
employee header data
DATA: FS_EMPHDR_DATA LIKE Z1EMHDR.
employee weekly details data
DATA: FS_WEEKDET_DATA LIKE Z1WKDET.
client details data
DATA: FS_CLIENTDET_DATA LIKE Z1CLDET.
employee monthly summary data
DATA: FS_SUMMARY_DATA LIKE Z1SUMRY.
total hours and amount for the summary segment
DATA: TOTAL_HRS_MONTH TYPE I,
        TOTAL_AMT_MONTH TYPE I.
Database Tables
Application data tables
TABLES: ZEMPDETAIL, ZEMPWKDET.
Internal tables
DATA:
    weekly details - appplication data
        IT_WKDET LIKE ZEMPWKDET OCCURS 0 WITH HEADER LINE,
    data records
        INT_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE,
    communication idocs geneerated
        IT_COMM_IDOCS LIKE EDIDC OCCURS 0 WITH HEADER LINE.
Program logic
********************Select Application Data***************************
SELECT SINGLE * FROM ZEMPDETAIL WHERE SSN = P_SSN.
IF SY-SUBRC NE 0.
     MESSAGE E001 WITH P_SSN.
     EXIT.
ENDIF.
SELECT * FROM ZEMPWKDET INTO TABLE IT_WKDET WHERE SSN = P_SSN.
IF SY-SUBRC NE 0.
     MESSAGE E002 WITH P_SSN.
     EXIT.
ENDIF.
********************Build Control Record******************************
Fill control record information
CONTROL_RECORD_OUT-MESTYP = P_MESTYP.
control_record_out-idoctp = c_monthly_report_idoc_type.
control_record_out-rcvprt = 'LS'.
control_record_out-rcvprn = p_logsys.
********************Build Data Records********************************
*--Employee header--
fill the employee header information
FS_EMPHDR_DATA-LNAME = ZEMPDETAIL-LNAME.
FS_EMPHDR_DATA-FNAME = ZEMPDETAIL-FNAME.
FS_EMPHDR_DATA-SSN   = ZEMPDETAIL-SSN.
FS_EMPHDR_DATA-DOB   = ZEMPDETAIL-DOB.
fill the administrative section of the data record
INT_EDIDD-SEGNAM = C_HEADER_SEGMENT.
INT_EDIDD-SDATA = FS_EMPHDR_DATA.
append the employee header data record to the IDoc data
APPEND INT_EDIDD.
*--Employee weekly details--
LOOP AT IT_WKDET.
fill the weekly details for each week
    FS_WEEKDET_DATA-WEEKNO = IT_WKDET-WEEKNO.
    FS_WEEKDET_DATA-TOTHOURS = IT_WKDET-TOTHOURS.
    FS_WEEKDET_DATA-HRLYRATE = IT_WKDET-HRLYRATE.
add administrative information to the data record
    INT_EDIDD-SEGNAM = C_WEEKLY_DETAILS_SEGMENT.
    INT_EDIDD-SDATA = FS_WEEKDET_DATA.
append the data for the week to the IDoc data
    APPEND INT_EDIDD.
Client details of each week
    FS_CLIENTDET_DATA-CLSITE = IT_WKDET-CLSITE.
    FS_CLIENTDET_DATA-WORKDESC = IT_WKDET-WORKDESC.
add administrative information to the data record
    INT_EDIDD-SEGNAM = C_CLIENT_DETAILS_SEGMENT.
    INT_EDIDD-SDATA = FS_CLIENTDET_DATA.
append the client details for the week to the IDoc data
    APPEND INT_EDIDD.
ENDLOOP.
*--Employee monthly summary--
compute total hours and amount for the month
LOOP AT IT_WKDET.
    TOTAL_HRS_MONTH = TOTAL_HRS_MONTH + IT_WKDET-TOTHOURS.
    TOTAL_AMT_MONTH = TOTAL_AMT_MONTH + ( IT_WKDET-TOTHOURS *
                                          IT_WKDET-HRLYRATE ).
ENDLOOP.
fill the summary information
FS_SUMMARY_DATA-TOTHRS = TOTAL_HRS_MONTH.
FS_SUMMARY_DATA-TOTAMT = TOTAL_AMT_MONTH.
condense the summary record fields to remove spaces
CONDENSE FS_SUMMARY_DATA-TOTHRS.
CONDENSE FS_SUMMARY_DATA-TOTAMT.
add administrative information to the data record
INT_EDIDD-SEGNAM = C_SUMMARY_SEGMENT.
INT_EDIDD-SDATA = FS_SUMMARY_DATA.
append summary data to the IDoc data
APPEND INT_EDIDD.
*************Pass control to the ALE layer****************************
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
       EXPORTING
            master_idoc_control            = control_record_out
       TABLES
            COMMUNICATION_IDOC_CONTROL     = IT_COMM_IDOCS
            MASTER_IDOC_DATA               = INT_EDIDD
       EXCEPTIONS
            ERROR_IN_IDOC_CONTROL          = 1
            ERROR_WRITING_IDOC_STATUS      = 2
            ERROR_IN_IDOC_DATA             = 3
            SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
            OTHERS                         = 5.
IF SY-SUBRC NE 0.
     MESSAGE E003 WITH P_SSN.
ELSE.
     LOOP AT IT_COMM_IDOCS.
       WRITE: / 'IDoc generated', IT_COMM_IDOCS-DOCNUM.
     ENDLOOP.
     COMMIT WORK.
ENDIF.

How to create Inbound Idoc from XML file-Need help urgently

Hi,
can any one tell how to create inbound Idoc from XML file.
we have xml file in application server Ex. /usr/INT/SMS/PAYTEXT.xml' we want to generate inbound idoc from this file.we are successfully able to generate outbound XML file from outbound Idoc by using the XML port. But not able to generate idoc from XML file by using we19 or we16.
Please let me know the process to trigger inbound Idoc with out using XI and any other components.
Thanks in advance
Dora Reddy

Hi .. Did either of you get a result on this?
My question is the same really .. I am testing with WE19 and it seems SAP cannot accept an XML inbound file as standard.
I see lots of mention of using a Function Module.
Am I correct in saying therefore that ABAP development is required to create a program to run the FM and process the idoc?
Or is there something tht can be done with Standard SAP?
Thanks
Lee

Re: ME51n through Inbound Idoc

Hi Expert,
Below is the required set up.
"A non-sap system will generate a textfile and the textfile will be push to SAP automatically to trigger automatic creation of PR."
This is my suppose approach but am not sure if this is feasible and how...
1. The text file be output in a ftp server or in a unix directory.
    the text file contain all the info needed to create a purchase
    request.
2. FTP or unix script will push this file to SAP by means of unix or ftp script..
   - any ftp script or unix script for this
3.SAP will acknowledge the textfile
   3.1 trigger event that will generate inbound idoc
       - how to set up the IDOC
   3.2 the inbound idoc will be use to create the PR
       - a customize program running in a background mode which as
         a mode of trigger event
   3.3. the customize program is made of bapi_create_purchase
Does anyone have this requirement before?, any other alternative or better approach to accomplish this? Thanks in advance..
She

Hi,
Please use BAPI_REQUISITION_CREATE to accomplish this.. You'd have to make a remote call and pass the data from the 3rd party system in to the BAPI's structure as a string and it is the nsorted out based on the fields in teh structure..

Inbound IDoc not getting generated in XI System

Hi all,
I have created a scenario following the given weblog:
/people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements
The first half of this scenario is working fine and the idoc data is getting posted into the the oracle table successfully.
The business process is successfully sending the acknowledgement IDOC 'ALEAUD' to the XI server using an HTTP Receiver Channel.
The problem is that no inbound IDOC can be seen in the XI system using tcode we05.
Next the xi system has to send the same IDoc to the R/3 system. But as no IDoc is getting generated in XI, nothing gets sent to R/3.
Can anyone suggest what could be the possible error.
Pls help.
Regards,
Neetu

Hi,
You will not see that IDOC in WE05 of the XI system. You can see that only in SXMB_MONI. XI system will not store any IDOC. When it enters XI it is a XML message and it will not post any IDOC that you can see in WE05.
If you need to send the IDOC back to R/3 system, you can use BPM and send back the IDOC to R/3. If you need few details from Oracle tables that is to be sent back to R/3 then get those values from Oracle tables and fill in the same IDOC and send it back to R/3.
Try this and let me know.
Thanks,
Prakash

Workitem is not generating for an Inbound Idoc

Hi All,
The problem I am facing, when inbound idoc is processing in SAP, if there are any errors occurred, it would generate a work item and that will be sent to user Inbox (SBWP) as per the workflow. Here it is not generating a work item for an inbound idoc where is there is an error. So user is not receiving work item mail to inbox, to check about the idoc error. This idoc has been processed through the function module.
Could you please let us know your input on this issue.

Hi Hitu,
The problem could be at multiple places.
To debug check the workflow which sends the workitem to the user when an error occurs.
Check if this workflow is getting triggered when the error occurs. If yes, then check the step whre this workflow fails.
Else, check the event linkage of this workflow and check if the associated event is getting triggered or not. If yes, check if the event linakge is active for the workflow.
There could be other places as well to diagnose the error.
Check if these inputs gives you some direction.
Regards,
Saumya

Inbound IDoc to generate Billing Document - t.code VF01

Hi,
which is the inbound idoc to trigger Billing Document.
pls suggest
thanks in advance...
Regards,
Balaji

Hi,
>IDOC name- INVOIC.INVOIC02
INVOIC02 can only be used as outbound from VF01 not as inbound (at least in standard)
unless you know a process code that can be used for inbound?
in general sales invoice can only be created via interface with the use of ERS (selfbilling) scenario
but I'm not sure if this is what you need
Regards,
Michal Krawczyk

Problem with user exit EXIT_SAPLIEDI_001 for Inbound Idocs in replacing G/L

Hello all,
I am currently facing an issue where my IDOC where exit EXIT_SAPLIEDI_001 is not appearing to work properly.
Basically I am using the FM that processes the inbound idoc (IDOC_INPUT_INVOIC_FI) to post an accounting document. We needed a solution where we need to substitute one of the G/L Accounts.
The current process in our SAP system is that we are creating a billing document which automatically generates the output type (running: program rsnasted subroutine edi_processing) to create and process the inbound idoc.
So I discovered FM EXIT_SAPLIEDI_001 which exports company code and G/L Account back does this.
In this exit, Since I needed to get data from the IDOC, I used the logic ASSIGN: ('(SAPLIEDI)IDOC_DATA[]') TO <fs_edidd> to get the DATA Records for further processing.
During the development and testing phase in the Sandbox system this works.
However when we moved this to production we encountered a situation where the G/L account was not being substituted so were assuming EXIT_SAPLIEDI_001 is not working properly. However when I reprocess this in production either by running the idoc with errors RBDMANI2 or BD87 the IDOC is properly posted and the G/L Account is substituted as well as if I try to repeat the output type of the billing document. So there are instances when in the actual business scenario it does not work except when I reprocess it.
I was wondering if there are any ideas why this could have happened?
Oh ... I also noticed when we transported the objects of the exit. When I try to double click the subroutine I made inside the exit it said the object does not exist. I had to generate the function group of FM EXIT_SAPLIEDI_001 in SE80 in production for it to reflect. I was wondering if this could have caused the issue.
Well I hope to hear from you.
Regards
Edited by: Rob Burbank on Dec 6, 2011 1:03 PM

Hi,
Check in t.code CMOD whether project is active or not (Activate the Project)
BR,
Vijay

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

Creation of FM for Inbound Idoc

Hi abap gurus,
I need to create a function module to generate an inbound idoc form a non SAP system system to SAP system .How can I send the data to the IDOC segments ? do I need to use EDIDD structure or I can do it without EDIDD structure ?
Thanks in advance .

Hi,
If u need to send data to the IDOC segments, it is better to use the EDIDD structure.
Edited by: sharin varghese on Jul 21, 2008 1:40 PM

Creation of Inbound Idoc for the Outbound Idoc in same client

Hi,
My requirement:
Whenver an PO is created an Outbound IDOC is generated in system ABC with client 100.I want to pass this IDOC data to create an Inbound Idoc for Sales Order(SO) in the same client.
It would be helpful if anyone can answer on how to Transfer the Outbound Idoc after it crosses the port.
I found there is a field for function module in WE21,can this be used to get the requirement done.
Please suggest.
Regards,
Amar

Example of a program that create and post an inbound idoc....maybe that will help you:
report zzinbound_idoc.
data: g_idoc_control_record like edi_dc40 occurs 0 with header line.
data: g_edidd like edi_dd40 occurs 0 with header line.
data: g_e1bpache09 like e1bpache09.
parameter: mode type c default 'A'.
refresh: g_idoc_control_record, g_edidd.
clear: g_idoc_control_record, g_edidd.
*-Build Control Record -*
g_idoc_control_record-mestyp = 'ACC_DOCUMENT'. "Message type
g_idoc_control_record-idoctyp = 'ACC_DOCUMENT03'. "IDOC type
g_idoc_control_record-direct = '2'. "Direction
* Receiver
case sy-sysid.
when 'DE2'.
 g_idoc_control_record-rcvpor = 'SAPDE2'. "Port
 g_idoc_control_record-rcvprn = 'IDOCLEGACY'. "Partner number
endcase.
g_idoc_control_record-rcvprt = 'LS'. "Partner type
g_idoc_control_record-rcvpfc = ''. "Partner function
* Sender
g_idoc_control_record-sndpor = 'A000000002'. "tRFC Port
case sy-sysid.
when 'DE2'.
 g_idoc_control_record-sndprn = 'IDOCLEGACY'. "Partner number
endcase.
g_idoc_control_record-sndprt = 'LS'. "Partner type
g_idoc_control_record-sndpfc = ''. "Partner function
g_idoc_control_record-refmes = 'Customer clearing'.
append g_idoc_control_record.
*-Build Idoc Segments -*
*---E1KOMG
clear g_edidd.
clear g_e1bpache09.
g_edidd-segnam = 'E1BPACHE09'.
g_edidd-segnum = 1.
move g_e1bpache09 to g_edidd-sdata.
append g_edidd.
*-Create idoc -*
*-Syncronous
if mode = 'S'.
call function 'IDOC_INBOUND_SINGLE'
 exporting
 pi_idoc_control_rec_40 = g_idoc_control_record
* PI_DO_COMMIT = 'X'
* IMPORTING
* PE_IDOC_NUMBER =
* PE_ERROR_PRIOR_TO_APPLICATION =
 tables
 pt_idoc_data_records_40 = g_edidd
 exceptions
 idoc_not_saved = 1
 others = 2.
if sy-subrc <> 0.
 message id sy-msgid type sy-msgty number sy-msgno
 with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
*-Asynchronus
else.
call function 'IDOC_INBOUND_ASYNCHRONOUS'
 in background task as separate unit
 tables
 idoc_control_rec_40 = g_idoc_control_record
 idoc_data_rec_40 = g_edidd.
commit work.
endif.
write: / 'Well done!'.

Create shipment from inbound IDOC SHPMNT05 ?

Hello All,
I would like to create an individual shipment when i receive from a partner an inbound IDOC.
I'm using Message type SHPMNT, Basic Type SHPMNT05, Process Code: SHPM and testing in WE19 via FM IDOC_INPUT_SHPMNT.
How can I start the creation of the shipment with this inbound IDOC ?
Is it possible ? or is it necessary to develop in user-exit the code to create shipment with function module (which one ? BAPI_CREATE_SHIPMENT ?)?
Thanks a lot,
My

Hello Reddy
thanks for your answer.
is there particular customizing to be done ?
i exactly use function BORES_IDOC_INPUT_SHPMNT
The inbound idoc is generated but i have the following status message 51 "Application document not posted"
What does it mean ? a problem of data in the inbound IDOC to create the shipment ?
Thanks a lot
MY

Send mail to a specific user group when an Inbound Idoc processing fails

I am using standard Message type DEBMAS, but the process code is customed (say ZDEBM as the function module is customed). Can you tell me what configurations are required to activate the error notification message to a user when the inbound idoc fails?

hi,
i think u need to check tcode swu3 for automatic workflow customizing and check in we40 (error AND STATUS PROCESSING) whether the processing code is assigned to the workflow task.
if it is assigned,the workflow will be automatically triggered and the mail will be sent to the user by itself.
ALE error handling uses workflow. A standard task is provided for each message type. Task TS20000051 is used for all BAPIs.
Workflow functions as follows:
A task (work item) is generated for the error handling and stored as a message in the inboxes of the employees responsible.
If one of these employees processes the work item, the standard task method for error handling is started. The user can, for example, restart IDoc processing.
If the IDoc is processed successfully, the work item is deleted from the inboxes of all the employees involved.
For this procedure to function, the employees responsible for a particular message type and partner (sender or receiver) must be defined as follows:
1. A hierarchy of organizational units (for example, "sales office") and positions (for example, "customer officer for customer X") is created and employees are assigned to it.
2. The standard tasks for error handling (for example, an error related to an inbound sales order) are assigned to the relevant organizational units or positions (for example, "sales office").
3. The organizational unit, position or employee responsible for dealing with the error are specified for each partner and message type in the partner profiles.
If an error occurs, the system determines:
1. The employees responsible using the staffing schedule of the organizational unit or position linked to the standard task.
2. The employees defined in the partner profiles (using position, user ID, or organizational unit).
3. The employees appearing in both groups represent those who will receive a work item in their inboxes.
regards,
pankaj singh

Generate inbound IDOC

Similar Messages

Maybe you are looking for