Outbound IDOCs for Functional Location

Hi experts
We are planning to use IDOCs for interfacing SAP and Legacy system using XI.
THis will be an outbound interface as we will be updating the legacy system with SAP.Therefore I am looking for a standard outbound IDOC for functional location.
So far I have not found one. Can you advise the outbound IDOC for Functional location ?
Another question I have , I have found some IDOC's but they are not released , Is there a way to release the IDOC's, what needs to be done for this.
Many Thanks
Regards
Gaurav

Hi Vinod,
This is the case for the 2 outbound Idocs from ECC to SNC for which settings have been maintained to send them immediately:
1. PORDCR1
2. STPOD
I have asked my PI team to check the PI port / PI cache. Will keep the thread updated if theres any resolution.
Regards,
Bharath

Similar Messages

Idoc for functional location

Hi all,
We have to send the functional location details using idocs.
Please send me the steps involved from scratch.
Also send some good material for beginners.
Thanks in advance
Regards,
Kashyap Ivaturi

Hi Kashyap,
Plz go through these links, I found very helpful I got these from one of the post in sdn.sap
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
Check these step-by-step links
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/ccab6730-0501-0010-ee84-de050a6cc287
https://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/8fd773b3-0301-0010-eabe-82149bcc292e
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/3c5d9ae3-0501-0010-0090-bdfb2d458985
http://idocs.de
For more info on idocs revert.
Thanks
Mohinder Singh Chauhan

Function Module to Generate Outbound IDOC for Sales Documents

Hello Experts,
Can someone please help me, I need to know which function module to use in order to generate the outbound IDOC for sales documents. Some of the fm's I have come across are the following:
IDOC_OUTPUT_ORDERS, but actually for Purchase Orders
IDOC_OUTPUT_ORDRSP, but did not generate any IDocs for my sample Sales Order.
Points will be given for any help provided.
Thanks in advance.

Hi Nagaraj,
I tried using the IDOC_OUTPUT_ORDERS but I keep getting an error that the Purchase Order <xxx> does not exist, even though the document I tried is a sales order. For everyone's reference here is the code:
form process_data.
DATA v_idoc       TYPE edidc-docnum.
DATA i_edidd      TYPE TABLE OF edidd.
DATA wa_idoc_ctrl TYPE edidc.
LOOP AT i_nast INTO wa_nast.
    CLEAR i_msgs[].
    CALL FUNCTION 'WFMC_PROTOCOL_GET'
      EXPORTING
        cps_nast        = wa_nast
      tables
        messages        = i_msgs
     EXCEPTIONS
       NOT_FOUND       = 1
       OTHERS          = 2.
    LOOP AT i_msgs INTO wa_msgs WHERE arbgb EQ 'E0'.
*--- Check first if there is an IDOC
      IF wa_msgs-msgv1 IS INITIAL.
        CONTINUE.
      ENDIF.
      v_idoc = wa_msgs-msgv1.
      CLEAR i_edidd[].
      CLEAR wa_idoc_ctrl.
      CALL FUNCTION 'IDOC_READ_COMPLETELY'
        EXPORTING
          document_number                = v_idoc
        IMPORTING
          IDOC_CONTROL                   = wa_idoc_ctrl
*         NUMBER_OF_DATA_RECORDS         =
*         NUMBER_OF_STATUS_RECORDS       =
        TABLES
*         INT_EDIDS                      =
          INT_EDIDD                      = i_edidd
        EXCEPTIONS
*         DOCUMENT_NOT_EXIST             = 1
*         DOCUMENT_NUMBER_INVALID        = 2
          OTHERS                         = 3.
      CALL FUNCTION 'IDOC_OUTPUT_ORDERS'
        EXPORTING
          object                              = wa_nast
          control_record_in                   = wa_idoc_ctrl
*       IMPORTING
*         OBJECT_TYPE                         =
*         CONTROL_RECORD_OUT                  =
        tables
          int_edidd                           = i_edidd
*       EXCEPTIONS
*         ERROR_MESSAGE_RECEIVED              = 1
*         DATA_NOT_RELEVANT_FOR_SENDING       = 2
*         OTHERS                              = 3
      IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      COMMIT WORK.
    ENDLOOP.
ENDLOOP.

Change pointer for functional location- deletion flag & activation status

Hello,
Im trying to use change pointer for functional location outbound interface. I did all required settings in BD52. The problem is with deletion flag and acive/deactive status.
I found that those two are stored in:
table     field
TAPL     LOEKZ
TAPL     PARKZ
The problem I have is that I cannot find the object for those table, and due to that it cannot be customized in BD52.
Could You please advise which object class should I use or alternatively which other table/field and object should I type in to activate change poiters for deletion flag and active/ not active status?
For object IFLO, and its table (IFLOT, IFLOTX, ILOA)- there is no field for del flag and active status.
Thanks in advance.

Hi, standard didnt let us fulfilling this requirement. What we did- we extended table IFLOT with additional field for the status and used an user exit when saving FL, to take the value (status) from table JEST/TJ02T and copy the value to the newly created field. Then BD52, iflo, iflot, and the new field and it worked. Of course the function module for the message type (BD60) had to be changed to add this status value in additional segment/field for the idoc. Hope this will help You, as there is a lot of technical background behind it, and this is only functional overview.
rgds.

Outbound IDoc for Goods Movement

HI
We need to generate XML files for goods movement posted in SAP at Goods Receipt (MIGO) and Post Goods Issue (VL02N). Requirement is asynchronous update where the receiving system will poll the xml file at the end of the day.
I have not been able to find any standard outbound idoc for goods movement.Can someone advise how they tackled any similar requirement? Any other approach also appreciated.
Thanks
Sriram

Answer to the question, which would be useful to all.
<b>MIGO</b>
MB_CF001 - Customer Function Exit in the Case of Updating a Mat. Doc.
This exit is called on update task, populate segments (edidc & edidd) of WMMBID02 (WMMBXY message type) and use MASTER_IDOC_DISTRIBUTE. Also you need to maintain the ALE Distribution model in WE64 for this message type.
Inside the code you can restrict based on movement type. No need to issue COMMIT.
<b>VL02N</b>
You can use BAdi: LE_SHP_DELIVERY_PROC to perform this.
Create Implementation and use the method SAVE_AND_PUBLISH_DOCUMENT.
Hope this help to others as well.

Outbound IDoc for AR Correspondence (Credit/Debit Memo)

We currently use the Print Correspondence function to generate automatic correspondence. In transaction OB78 we have each correspondence type linked to a print program which generates a .pdf "AR Invoice" via SAPScript.
Our new requirement is to generate an Outbound IDoc for the same miscellaneous AR Correspondence output. There does not seem to be any configuration means by which to generate an IDoc for these financial documents. Enhancement RFKORIEX only allows for fax or email.
Please advise how to generate IDoc via configuration without extensive coding.

We currently use the Print Correspondence function to generate automatic correspondence. In transaction OB78 we have each correspondence type linked to a print program which generates a .pdf "AR Invoice" via SAPScript.
Our new requirement is to generate an Outbound IDoc for the same miscellaneous AR Correspondence output. There does not seem to be any configuration means by which to generate an IDoc for these financial documents. Enhancement RFKORIEX only allows for fax or email.
Please advise how to generate IDoc via configuration without extensive coding.

Outbound IDOC for Goods Reciepts (MBGMCR01)

Hi All,
We need to send outbound idoc for goods movement GR (Basic idoc type- MBGMCR01), the problem is how to trigger that idoc, through output type or is there any other way to do it,
If it is through output type what all settings we need to configure for this.
Thanks in Advance
Regards
Shazia

Hi Shazia,
Speaking in terms of EDI Idocs, system is not prepared for send Goods Receipts because normally is an incoming message not the opposite. All the output messages you can find are for printing purposes.
So you need to configure everything for Output Determination and create a new function module to capture NAST message determination, retreive GR data, populate the Idoc and distribute it. Finally you have to create output process code, partner profile, port, rfc, distribution model, etc. etc.
Your starting point is next IMG activities to configure new output type for EDI medium for application ME: Material Management>Invetory management and Physical inventory>Output Determination.
Reward points if useful
Roger

Trying to change Inbound IDOC to Outbound IDOC for testing....

Hi Friends,
I am trying to do the following
1) In our legacy system SAP R/3 3.1H we have received an IDOC from our partner. This has been stored correctly.
2) We now need the same functionality in our SAP R/3 4.6C system so I have created the IDOC type + segments accordingly. I have also set up the partner profiles
3) We need test data but our partner can not send yet so the only other way is to send this INBOUND IDOC from 3.1H to 4.6C.
4) HOWEVER, i have tried everything to do this like using WE19 to edit the idoc, but I can not process it for OUTBOUND processing.... You can in 4.6C but there is no option in 3.1H.
HELP!! Rewards

Hi Friend,
        The test programs allow you to skip certain sections of the processing chain between applications to localize errors. However, they can also be used to simulate an entire business process (for example, purchase order on the customer side with posting of the purchase order on the vendor side) in an SAP System (without any other systems). For this reason, the test programs are an important tool for configuring the IDoc Interface and defining new IDoc types.
Use
You can use the test tool to generate an IDoc manually and send the IDoc for either inbound or outbound processing. You are not restricted to a specific port type. You can start with an IDoc type (an empty IDoc) or use an old IDoc as a template and edit the IDoc, that is, add segments or change data. This is a good way to test new IDoc types, in particular.
You can forward your new IDoc for standard inbound processing (checking partner profiles and so on). You can also call a function module directly. You can therefore test new function modules for new IDoc types.
Activities
·        Start the test tool with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Test Tool (WE19). You can use a template for your test IDoc.
You can choose IDoc types as a template, either directly or according to a specific message type. You can use the F4 Help for IDocs used as a template, which searches for IDocs by selection criteria, in the same way, for example, to IDoc Display. When an IDoc file is used as a template, the IDocs are read from this file and are available to you for selection. A default value for the IDoc file gives you the system using your test port which you can enter in IDoc Administration . This test port must therefore be of the file type. The default file is the inbound file entered there.
·        You generate the IDoc using .
The IDoc is displayed as a tree structure. If you do not use a template to create the IDoc type, at least one more segment must be added.
·        To create segments in the form of tree nodes (colored fields) place the cursor on an existing node (for example a control record at the top) and choose .
You can cut, paste or copy individual segments or entire segment groups by positioning the cursor on the relevant segment and selecting the required action from the Edit menu.
·        Click on the white fields to change data in the segments.
In the case of the control record, only the fields which are relevant for standard inbound processing are displayed. Do not forget the required entries in the partner profiles if you want to send the IDoc for standard inbound processing! You can also change all of the control record data by choosing All fields in the edit screen.
In the All fields editor screen you must enter the non-language specific partner function (for example AG for vendor). This is the only screen in the IDoc Interface in which the partner function is not translated into your language (in English AG becomes vendor VD) - in the partner profiles or in the IDoc display the field is always translated. Thus, you see the partner functions here in the way they are saved in the database. This is a unique value in the SAP System and therefore protected against mistakes.
·        The additional procedure depends on whether you want to test inbound or outbound processing.
Test: Outbound Processing from MC
Use
Use this test program if you have chosen the Message Control module and want to test generation of an outbound IDoc from an existing message status record (table NAST).
Prerequisites
You must be able to post the application documents which are to be converted into IDocs by the Message Control module correctly so that a message status record can be generated. In the case of the Materials Management (MM) and Sales and Distribution (SD) components, the following entries are required:
·        Customer or vendor records
·        Material records
·        Info records
·        MC condition record: The output medium 6 (for EDI) must be entered here. The condition records are maintained as messages from the respective application.
The appropriate file ports and partner profiles must exist in the IDoc Interface.
Outbound processing must be stopped when the message status record has been generated to allow the test program to intervene. To do so, you must set the Message Control dispatch time to 1 (output with selection run) in the corresponding condition record in the application. This test program, therefore, is simply used to start a selection run which retrieves the Message Control records and sends them for further outbound processing. The program is report RSNAST00, which is also generally scheduled with dispatch time 1 in live operation.
Activities
Once the application document has been posted, outbound processing stops after the message status record has been generated and is triggered again by the test program. Choose SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Outbound ® Outbound from MC.
Errors are stored in the Message Control processing log (document header) and in the status records of the IDocs. The status records, however, are only available if the IDoc was successfully generated.
Use
This test program selects one or more outbound IDocs and forwards them to the external system. You can choose the IDocs according to various criteria (for example, recipient or business message).
Prerequisites
You require outbound IDocs which were generated without errors (no error status). The partner profiles, therefore, must be maintained completely.
Outbound processing must stop when the outbound IDocs have been generated to allow the test program to intervene. You can check this by setting the output mode to Collect IDocs in the partner profile for the IDoc Interface. If you now generate an outbound IDoc for the partner (for example, using the application or the test tool), the IDoc is only generated in the SAP System and is not forwarded to the external system. This test program, therefore, is simply used to start a selection run which retrieves your IDoc(s) and sends them to the external system. The program is report RSEOUT00, which is also generally scheduled with the output mode Collect IDocs in live operation.
Activities
You start the test program by choosing SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Outbound ® Outbound from IDoc (WE14).
You can decide whether the output mode is set to Start subsystem or Do not start subsystem in the partner profile. This defines whether the external (sub) system processes the IDocs further.
Use
This program is used to test whether status confirmations for an outbound IDoc are sent correctly from the external system to the SAP System. The port type here must be set to File.
Prerequisites
A correct status file which can be generated by an EDI subsystem, for example, is required. The status file must refer to an existing outbound IDoc in the SAP System. You can also generate such a status file yourself.
The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type File in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
Features
The SAP System reads the status file. The IDoc number contained in the file refers to the outbound IDoc, to which the status confirmation relates. The confirmed statuses are credited to the relevant IDoc in the form of status records in the SAP System.
Activities
Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Status ® Edit Status File (WE17) and pass the inbound port, name and directory of the file. These entries overwrite the standard values which you have stored in IDoc administration using the test port.
Test: Inbound Processing: Modified Outbound File
Use
This program converts an outbound file with IDocs to a correct inbound file and sends the new file for inbound processing. The outbound file is not modified and can therefore be used more than once. The port type here must be set to File.
Prerequisites
You need a correct outbound file, for example, a file which is generated by the test tool or using a standard outbound processing. In this case, a port of the type File must be specified in the partner profile for the IDoc Interface, so that the IDoc(s) can be written to a file.
The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type File in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
Features
The program imports sender and recipient data as input parameters from the user. The program reads the IDoc file and changes the corresponding entries in the IDoc control record. The changed data is written to a second IDoc file at the operating system level.
Standard inbound processing is then triggered;
·        Reading the modified file
·        Generating the IDoc(s) in the SAP System
·        Processing in the application
Activities
Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Inbound ® Inb. Mod. Outb. File (WE12).
Set the sender and recipient data, as well as the outbound file and the inbound file to be generated (path and name). Your entries for the inbound file overwrite the standard values which you have stored in IDoc administration.
The recipient in this case is the SAP System. The port is used for identification purposes:
·        SAP (for example RSMITH
Test: Inbound Processing: Original Inbound File
Use
This program reads an inbound file and sends the file for inbound processing. If all data has been successfully read, the file is deleted.
Prerequisites
You require a correct inbound file. In this case, correct means that the:
·        Sender and recipient in the control record are correct
·        Direction in the control record is set to 2 (inbound)
·        Client in the control record and data records are correct or empty
The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type File in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
Features
The program reads the IDoc(s) from the inbound file and sends them for standard inbound processing (with processing within the application).
The file is deleted after being read successfully!
Activities
Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Inbound ® Inb. Orig. Inb.File (WE16) and pass the following data:
·        Inbound port
·        Name and directory of the file
These entries overwrite the standard values, which you have stored in IDoc Administration using the test port.
Thanks

Is it possible to generate outbound idocs for FI invoices? How?

Is it possible to generate Outbound idocs for FI invoices? How? or else i have to write program to get data in file and pass it to translator. Please help.

Dear Gabriel
Before letting you know the possibility, can you please let me know why you want such a requirement, since standard has not provided such copy control, to my knowledge.
As you would know order type KB is for consignment fillup where you are just transferring the goods from FG unrestricted to your own warehouse and that is why in standard you can see the copy control KB --> F8 which means you can raise proforma against delivery and not against fillup order.
So think of whether really you wanted to raise proforma against fillup order which is NOT recommended by SAP. However, still if you feel that the requirement is so to have, you can make the settings in VTFA.
thanks
G. Lakshmipathi

Generate outbound idoc for Customer Master

Hi Developers,
I have requirement to generate outbound IDOC for Customer Master Data. I need to send customer master data through an Outbound IDOC. Can we generate an outbound DEBMAS06 idoc? Can someone help me finding a solution to this problem?
Thanks in advance for helping.
Regards,
Gajendra

Hi,
If you have done all the required settings (logical system, partner profiles, distribution model), then either transaction BD10 / BD14 will help you generate the IDOC.
If you want to send the idocs automatically, then you will to configure some program.
Unlike transaction data, Master data IDOCS are not triggered immediately, you will have to do the required configuration in SPRO.
Transaction SPRO
SAP Customizing Implementation Guide -->
SAP Web application Server --> Application Link Enabling --> Modeling and Implementing Business Processes -->
Master Data distribution --> Replication of Modified Data --> Creating IDOCS from Change Pointers
Take a look at this thread.
Re: automatic Idoc outbound
Regards,
Ravi
Note : Please mark the helpful answers
Message was edited by: Ravikumar Allampallam

Updating and deleting Partner functions for functional location

Hi ,
I am having a requirement of updating and deleting partner function for functional location .
If anyone can suggest some BAPI or function module for same .
Thanks n Regards
Manik

Hi Fritz,
Thank you for your response,
My need is to create a PARTNERS for the FUNCTIONAL LOCATION.
LET ME DESCRIBE IT.
WHEN I AM CREATING A FUNCTION LOCATION USING IL01, AS I ENTER A FUNCTIONAL LOCATION AND PRESS ENTER IN THE NEXT SCREEN.
AND
I NEED TO ENTER THE PARTNERS FROM THE DROP DROWN MENU GOTO ->PARTNERS
WHICH TAKES ME TO THE NEXT SCREEN WHERE I NEED TO FILL THE INFORMATION IN THE TWO FIELDS : FUNCT & PARTNER.
I need a partner for the functional location that i mentioned above.and i need to upload that information in through Emigall.
So my query was that can we customize that partner for this functional location and if yes, what should the constraints,
what are steps required? Do we require a custom service module?
Regards,
Robert.

Tables for Functional location/equipment in Sales Area

Hi ,This is sivakumar ...
h2.
I wanna know Tables for Functional Location/equipment in Sales area under the Customer Service erena.

I know the sales order number, header and item ..
I need other parameters to use this table....

IDOC for Functional Areas

Hi,
I am looking for some IDOC for the creation of Functional Areas.
Transaction : FM_FUNCTION
Table : TFKB
I have not find any yet, do you know how can i fine the IDOC or maybe it does not exist any IDOC for Functional Areas?
Thank you,
Regards,
Zheng

As far as I know, there is no standard IDoc for it. However, to give you a pointer, you can look at FM FM_FUNC_AREA_CREATE or BUS0023 (Functional Area).
Thanks & regards,
Hadiman

If output type is missing in PO, can system create a Outbound IDOC for that

Hi
Scenario: sales order should get generated in anoter system once PO is saved in first system. But this is not happening for a new vendor. I checked & found that output type is missing in PO. Asked user to provide another PO for which SO was created. I checked that PO, here also output type is missing.
I am surprised that if output type is missing in PO, can system create a Outbound IDOC for that PO? If yes then I am not aware of this process.
Please help me in analyzing this problem.
Regards
Sapmm12

Hi Sridhar,
Thanks for your replay.
I checked for other vendor also. condition records does not exist in NACE for any of them. But user is claiming that sales aorder is getting created for those PO. Though I have asked them to provide the sales order number & possibly outbound IDOC number for at least one vendor.
I tried to search IDOC number with reference to PO number but system is taking too much time & ending with run ime error. Because I do not have details of partner, receiver not even message type. Neither I have any process document which can explain how this process works?
any other approach which may work here?
Regards
sapmm12

Function module like ENQUEUE and DEQUEUE for function location.

Hi All,
I should be highly appreciate if any one help me for locking function module like ENQUEUE and DEQUEUE
for function location.
Thanks
Shaw

Hi,
You can either use the standard way of locking by using :
data:lv_varkey          TYPE rstable-varkey.
concatenate functional_location sy-mandt into lv_varkey .
*   Lock table
    CALL FUNCTION 'ENQUEUE_E_TABLEE'
      EXPORTING
        mode_rstable   = 'E'
        tabname        = 'IFLOS'
        varkey         = lv_varkey
      EXCEPTIONS
        foreign_lock   = 1
        system_failure = 2
        OTHERS         = 3.
*     Unlock table
      CALL FUNCTION 'DEQUEUE_E_TABLEE'
        EXPORTING
          mode_rstable = 'E'
          tabname      = 'IFLOS'
          varkey       = lv_varkey.
Or,
As mentioned above create a lock object via transaction SE11.
Go to transaction se11:
--> Enter lock object name e.g EZ_IFLOS
--> Click on create
--> Enter description
--> Click on tables tab
--> Enter 'IFLOS' as table name
--> select lock mode
--. click on save and activate.
2 function modules will be created as DEQUEUE_EZ_IFLOS and ENQUEUE_EZ_IFLOS .
Regards.

Outbound IDOCs for Functional Location

Similar Messages

Maybe you are looking for