Outbound IDoc setting through ACC_GL_POSTING

Dear Members,
I am willing to post an IDOC ( Msg type : ACC_GL_POSTING or any other) for FI Transaction G/L Posting without using any user exits. Is there any way to post it with standard setting???
Thanks in advance,
Audy.

Hi Karun,
Actually, I was trying to create an IDoc'ACC_GL_POSTING' for certain G/L postings without using MASTER_IDOC_DISTRIBUTE function explicitely ; but finally got configuration for cross-system company code setting in SALE transaction. This can create IDoc FIDCC01 or FIDCC02 whenever an FI doc. is posted. We just need to create a partner profile for it...
Is there any other setting which can generate IDoc ACC_GL_POSTING in similler way??...Like using some SPRO setting??
Also while posting same IDOC i.e. 'ACC_GL_POSTING' using standard process code 'BAPI' , we need many conversions , custom checks etc....
My problem is, Which is better way?? write a big code in exit of posting program or write separate Z-posting program tio post IDoc..
Thanks and regards,
Audy.

Similar Messages

Handling outbound IDOC errors through workflow TS00007989

Hi,
I want to sent an notification e-mail to external mail box when an outbound idoc has an error status. This needs to be achieved through a workflow template.
I noted that there is a standard task TS00007989 in WE40 which is used for handling outbound idoc errors.
Moreover i couldnt find any trigerring events for the above task.
Can any one help me with a step by step guide for achieving this.
Regards,
Krishnakumar

Hi,
the single step task TS00007989 that you see is NOT TRIGGERED thru' any BO's event. It is created by the std. pgm RSEWFERR. If you go to the wflow log of the witem generated by it, you will see the Creator.
And you can control the activation / deactivation of these single step tasks for various inbound and outbound Error IDOC's thru' Transaction WE46.
If you want, create a single step task of your own and maintain that task here. But, you will ahve to know the exact BO like IDOCORDERS or IDOCEMBMAS etc. or look for events triggered by General IDOC objects like IDOCAPPL.
Hope this helps.
venu

Outbound IDOC WPDTAX not getting generated

Hi
I am not able to generate outbound IDOC WPDTAX through WPMA transaction.
We are using TAXUSJ as the tax procedure.
Tax Condition type UTXJ and JR1 has been maintained in the system.
On looking at the code against WPMA ,
POS_TAX_GET is called to calculate taxes.
It does not have a fetch against all the condtion tables for tax.
The above condition has been maintained in table A053.While the above program fetches data against only A003.
Can somebody help?
Regards,
Amit.

Hi Amit,
For TAXUSJ, the conditions maintained are time dependent conditions.
However , IDoc type WPDTAX01 does not support time dependent conditions.
Only time independent conditions will be transferred with the help of Idoc type WPDTAX01.
http://help.sap.com/erp2005_ehp_03/helpdata/EN/3f/81e33bfa5d11d38d1f080009d10d9a/frameset.htm
Regards,
Lisa

Handle Idoc errors through workflow

How to handle inbound idoc errors through workflow and How to handle outbound idoc errors through workflow
Thanks,
Asha

in transaction SALE go to menu Basic Settings/Perform Automatic Workflow Customizing
then in WE46 you can assign a workflow task to various errors
in partner profiles (WE20) you can assign post processing agent per partner/message type

Outbound Idoc error handling through workflow

Hi,
I am trying to set up the workflow for outbound error handling. I found that there is a task TS00007989 which need to set up.
How this task can be triggered when outbound idoc error occurs in the system?
Kr,
Vithalprasad
Edited by: Vittalprasad on Jun 9, 2010 11:52 AM

Hi,
Have a look
Outbound IDoc Error Handling via Workflow
Outbound idoc error handling through workflow

Outbound Idoc through Workflow in CRM

Hello,
Consider this scenario, I need to create an opportunity document through Idoc inbound in CRM 4.0. There are certain validations done at the XIF layers as well as the application layer.
In case if there are any errors in the Idoc or errors the opportunity document created(application level errors), I need to send an outbound Idoc containing complete inbound Idoc data with certain rejection codes.
Can some body let me know the best way to achieve this. I
If this can be achieved through workflow, please provide the complete details on how to go about this.
Thanks In Advance,
Kiran

Hello,
Consider this scenario, I need to create an opportunity document through Idoc inbound in CRM 4.0. There are certain validations done at the XIF layers as well as the application layer.
In case if there are any errors in the Idoc or errors the opportunity document created(application level errors), I need to send an outbound Idoc containing complete inbound Idoc data with certain rejection codes.
Can some body let me know the best way to achieve this. I
If this can be achieved through workflow, please provide the complete details on how to go about this.
Thanks In Advance,
Kiran

Post inbound as well as outbound IDOCs through a report

Hi all,
I have a specific requirement where i need to post an IDOC through a report which ressemble to WE05. This requirement implies for Inbound as well as Outbound for all message types. Can anyone let me know how can this be achieved. Please let me know if this can be acheived through any FM or method.
Regards
Simin.R

Hi,
To create a new inbound idoc use the following function module:
IDOC_INBOUND_SYNCHRONOUS
To Create a outbound idoc use the function module
MASTERIDOC_CREATE_* - search and decide based on your requirement.
Regards,
Baburaj

Outbound IDoc status set as 31

Hi Friends,
I am working on the outbound IDoc interface IDOC_OUTPUT_ORDRSP. I modify/add few segments based on the business conditions using the user-exit EXIT_SAPLVEDC_003 (ZXVEDU15). According to the business need, I have to set the IDoc status record as 31. Now IDoc is being created with status record as 30. Is there any way to set the status record with status 31 within the scope of this IDoc interface IDOC_OUTPUT_ORDRSP.
Pls let me know if any user exit for this same purpose. If not possible to set status explain me the reason for that.
Thanks
Hari

Hi,
You can use this standard program RC1_IDOC_SET_STATUS to change IDoc status 30 to another status.
If the program does't exits then try this ...
DATA: L_EDIDC_TAB LIKE EDIDC OCCURS 1 WITH HEADER LINE,
 L_IDOC_STATUS_TAB LIKE BDIDOCSTAT OCCURS 1 WITH HEADERLINE,
 L_IDOC_CONTROL LIKE EDIDC.
 L_IDOC_STATUS_TAB-DOCNUM = <your IDoc number>.
 L_IDOC_STATUS_TAB-STATUS = '68'.
 APPEND L_IDOC_STATUS_TAB.
 CALL FUNCTION 'IDOC_STATUS_WRITE_TO_DATABASE'
 EXPORTING
 IDOC_NUMBER = L_EDIDC_TAB-DOCNUM
 IMPORTING
 IDOC_CONTROL = L_IDOC_CONTROL
 TABLES
 IDOC_STATUS = L_IDOC_STATUS_TAB
 EXCEPTIONS
 IDOC_FOREIGN_LOCK = 1
 IDOC_NOT_FOUND = 2
 IDOC_STATUS_RECORDS_EMPTY = 3
 IDOC_STATUS_INVALID = 4
 DB_ERROR = 5
 OTHERS = 6.
Reward points
Regards
Message was edited by:
 skk

How to send Outbound IDocs through an RFC-enabled FM

Good day to all;
A partner system (AS/400) wants to use a Java Connection to execute a RFC Function Module, in SAP, that will then return a collection of IDocs.
Currently, the Function Module builds the IDocs, but I'm not exactly sure how to simply send those IDocs back to the AS/400.
If anyone can help in this regard, that would be great.
My current thoughts are to use Master_IDoc_Distribute, but then I imagine that requires a port configuration for the AS/400. And if this is the case, does that mean that SAP will send the IDocs back itself instead of using the RFC interface?

Hi Tavares,
If you want to send outbound IDoc to AS/400 (external system), you need to setup file port (t/code WE21).
For RFC interface, you need to setup RFC file port with RFC Destination (t/code SM59). In this case, SAP will send IDoc (individually or batch) to receiver system (AS/400). Perhaps you need a middleware for data transformation, if AS/400 does not perform data mapping for outbound IDoc.
For FTP interface, you need to setup flat/XML file port for outbound. then you can FTP the file to AS/400 later on.
In addition to file port configuration, you also need to setup partner profile for outbound parameter (t/code WE20) and the distribution model (t/code BD64).
Hope this will help.
Regards,
Ferry Lianto

How to trigger outbound IDOC when data changed in BP through Inbound IDOC.

Hi,
    In our system whenever we create a new Business Partner, these data is send across to SAP R/3 (as BDOC) and to Mainframe system (as outbound IDOC). Whenever we change any Business Partner record the data is send across to SAP R/3 (BDOC) and to Mainframe system (as outbound IDOC).
    This functionality is working fine.
    Currently we are getting a value for one standard field (Customer_Group3) of Business Partner as an inbound IDOC. The value of the inbound IDOC is reflecting in the field (Customer_Group3) in Business Partner Transaction. Once the inbound IDOC is received, the modified value is send across to SAP R/3 as BDOC. But the modified value is not send across to Mainframe system (outbound IDOC). The outbound IDOC is not getting triggered.
Kindly help

Is your mainframe system configured as Site in SMOEAC. If so are you using XIF Adapter.

Change Business Partner in CRM to trigger OutBound IDOC in R/3 system

Hi Team,
I am stuck on a requirement, We have a scenario were the Business Partner is created in CRM system
which creates a BDOC and is passed to R/3 system through an Inbound IDOC which triggers the Outbound IDOC to PI system. So far good.
The scenario we are getting stuck is when a Business partner is changed in CRM an IDOC triggered in R/3 system but this being a change the Change pointers are not called hence the IDOC which is supposed to be triggered for the PI system is not getting triggered.
Can you please tell me what steps should I take to trigger this Outbound IDOC from R/3 system?
I did some anlyasis and found a table which COM_BUPA_CALL_FU which contains a set of function module which is triggered in the sequence. Is this the solution or if you have any different do let me know.
Thanks,
Imran

Hi,
Did you add the entry for your new custom 'Z' long text inPITX Tcode in R3 side. Every long texts in CRM should be linked to R3 long text here. If there is no entry please add one and try changing the text in CRM.
Hope this helps,
Karuna.

About Orders05 outbound Idoc.

Hi,
I am using an outbound idoc of basic type Orders05 with an extension of the idoc header segment.This outbound idoc will get triggered once a PO is saved and sent through EDI.
I have to do an enhancement wherein I have to populate the mode of transport field(EXPVZ) and place of loading(LADEL) in the fields of the extended segment selecting them from EIKP depending upon the BELNR value in the header of the idoc(E1EDK01-BELNR).
I am unable to understand how do I populate the fields.
Could you please help me.
Thanks,
Sandeep.

HI,
see the below steps you will completely understand the processing outbound..
2.1 Outbound Interface
PROCESS DIAGRAM
Outbound Interface
1. Analyse Hierarchy Levels
2. Create New segment
3. Create New IDoc Type
4. Create New Message Type
5. Link Message with IDoc Type
6. Create an entry in EDP13 via transactions WE20 and BD64
7. Populate the Custom IDoc via ABAP Program
7b Error Handling
7c. Send Status Email
8. Test the Population of the Custom IDoc
Step 1 Analyse Hierarchy Levels:
Analyse the data relationships being processed in the interface. Define the appropriate hierarchical Parent-to-Child relationships.
Navigate to transaction code WEDI
Transaction WEDI displays the IDOC main menu. This allows navigation around the various development and control areas to create a customised IDOC.
Step 2 Create a new segment:
via wedi : Development - IDOC Segments or Transaction code WE31.
 Enter segment name and click on Create.
 The name of the segment type must start with Z1 , and have a maximum of eight characters.
 Enter description and enter the relevant field names and data elements.
 The segment should represent a structure in the program so for each field in the segment a field name and a data element must be defined.
 Save the segment and enter Person Responsible and Processing Person .
 Go to Edit and Set Release.
 Repeat this procedure for each new Segment in the IDOC.
Step 3 Create a new IDOC Type
via wedi Development - IDOC Types or Transaction WE30.
 Enter segment name (starting with Z), click on Basic Type and then Create.
 Create as new, enter Person Responsible and Processing Person and enter description.
 On Create Basic Type screen decide where segments should be inserted and go to Edit/Create Segment.
 Complete relevant fields in the Maintain Attributes screen:
 From the relevant segments created in Step 2 enter the Segment type and if mandatory segment.
 The Minimum and Maximum number of segments to be allowed in the sequence. (One minimum and one maximum if segment is mandatory).
 The Parent Segment and Hierarchy Level will be automatically created depending on where in the IDOC tree you decided to create that particular segment.
 Repeat this process for each segment needed in the IDOC type, deciding whether to add the next segments at the same level or as a Child.
 When IDOC created return to initial screen. Go to Edit and Set Release.
 Go to Transaction WE60 to view the IDoc Type you have created.
Step 4 Create new Message Type
via wedi Development - Message Types or Transaction WE81.
 Display/Change and click on New Entries
 Create a new Message Type and Save.
Step 5 Link Message Type to IDOC Type
via wedi Development - IDOC Type/Message or Transaction WE82.
 Display/Change and then click on New Entries.
 Enter Message Type, Basic Type (IDOC Type) and Release (46C) and Save.
Step 6 Create an entry in EDP13 via transactions WE20 and BD64.
The partner profile for the Idoc must be set up and generated in the transaction BD64 and transaction WE20.
 WE20 Add Message Type to appropriate Partner Type, Enter Message Type, Receiver Port and Idoc Type and Save.
 BD64 Create a Model View, Enter Sender and Receiver Ports, Attach Message Type. Go to Environment on Menu and click on Generate Partner Profiles and generate (not save) profile.
Step 7 Populate the custom IDOC via ABAP Program
See Test Program ZOUTBD_IDOC_TEMPLATE, Appendix IV.
 Create an Internal Table for each segment type, this should be exactly the same structure as the segment type.
 The control record is filled into a structure like EDIDC. The message type and the Idoc type for the Idoc must be populated into the eddic structure.
- PERFORM populate_Control_structure USING c_mestyp
 c_SEGMENT_type1.
 The data segments are filled into a structure like edidd-sdata; sdata and the segment name are populated into the edidd structure.
- PERFORM transfer_Parent_data_to_seg.
 The standard SAP function module MASTER_IDOC_DISTRIBUTE is called to pass the populated IDOC to the ALE Layer.
- PERFORM master_idoc_distribute.
 NOTE: This function module is only called for stand alone programs and Shared Master Data programs (SMD). It is not called when using extensions or output determination.
 The ALE Layer handles the sending of the IDOC to the receiving system.
 Error Handling (see Step 7b).
 Commit work.
Project Specific
Step 7b Error Handling Analyse which fields in the interface are mandatory for the receiving system and who needs to receive error notification.
 Declare a structure of type MCMAILOBJ for sending instructions.
 Enter values for the internal table based on structure MCMAILOBJ
 For selection processes, on SY-SUBRC checks and where fields are mandatory for the receiving system; insert Function Module MC_SEND_MAIL.
 Enter values in the following parameters: -
MS_MAIL_SENDMODE = B (Batch Mode)
MS_MAIL_TITLE = 'Mail Title'
MS_MAIL_DESCRIPTION = Error description (e.g. MATNR not given)
MS_MAIL_RECEIVER = Name of Receiver (To be determined)
MS_MAIL_EXPRESS = E (Express Delivery)
MS_MAIL_DLINAME = Leave Blank
MS_MAIL_LANGU = 'E' (Language)
MS_MAIL_FUNKOBJ_NAME = Leave Blank
TABLES
 MS_MAIL_CONT = I_MCMAILOBJ
Note:
It has to be determined separately for each interface how these errors and mail notifications are to be grouped dependant upon the number of errors that are potentially likely. One possible approach is to send an email for each reason for rejection and include all the records that failed for that reason in the mail notification. Another possible approach is to send an email for every failure.
When error checking for mandatory fields it is common SAP practice to reject a record on its first failure (irrespective of subsequent errors in that record)
Step 7c Send status mail
 Append to table I_MCMAILOBJ details of the time the interface was processed, how many Idocs were created and how many of these produced a status of 03.
 Select the user to receive the mail from ZINT_RECEIVER, using the name of the program as a key (SY-CPROG).
 Use function Module MC_SEND_MAIL to send a mail to the user containing the contents of I_MCMAILOBJ at the end of the interface processing.
Step 8 Test the population of the custom IDOC
via wedi IDoc - Display IDoc or Transaction WE02.
 Enter your message type and execute.
 Status should be green, double click on one of the Idocs you have created to view its contents.
 If a problem has occurred click on Status which will give you a description of the error.
 Drop down Data Records arrow and this should list the data in the IDoc in the correct hierarchical structure.
 Click on each individual segment and view the content to check that the correct data has been read.
 If you have UNIX access by using AL11 you can view the file that you have created.
Note:
For some interfaces it may be valid to send an empty file to SAP. This empty file is converted to the custom IDOC format expected by SAP. This custom IDOC will contain dummy information. In the inbound processing code, if the dummy information is identified then the processing of the IDOC is considered to be complete and the IDOC should then be assigned a successfully processed status of 53, even though it has not been processed at all.
rewards if useful
regards,
nazeer

Steps for configuring Outbound Idoc OILSHI01

Hi experts,
 can anybody tell me the steps how to configure an Outbound IDOC.
 It is better if somebody can take Shipment IDOC of IS-Oil - OILSHI01.
 if not anything else will also do.
 Kindly give me steps in detailed. Since i have never done this. Including
 distribution modle (BD64). in which case it generates the Automatic Partner
 profiles.?
<REMOVED BY MODERATOR>
Regards,
Umesh
Edited by: Alvaro Tejada Galindo on Apr 21, 2008 3:08 PM

Hi Umesh,
Sorry for the late reply. Let me clear your couple of misconceptions first.
Every idoc is an application idoc. That is, if an idoc is not attached to any application, then it doesnt make business sense to generate that idoc.
Secondly, an idoc is outbound or inbound depending upon its communication direction w.r.t. the sender system. If the idoc is going out from lets say R/3 system (where you are creating distribution model), then its an outbound idoc and if its coming inside, then its inbound idoc.
Now the further steps:
Since its a transactional data idoc, we dont generally go for change pointer activation. Kindly read the documentation to get more idea (if you dont have any then send me your mail id, i will send you a very good document). For transaction data, we use output type to trigger an idoc. Following are the steps to trigger an outbound idoc through output type.
However, remember that in this case, you need help of your functional consultant at every point so that you can clearly determine your application definations and configuration.
1. Go to transaction NACE. There you can see all the generic applications listed. Find out the one relavant to your idoc type from the functional person. If you select your relavant aplication, and click on the "Output types", you will see a list of all the output types for each business transaction defined for that application.
2. Again, ask your functional consultant, as to which output type is configured for your business transaction. Select that output type and go to "Processing routines".
3. There you will be able to see different ways in which the idoc can be triggered. Most of the time , we use processing routine "A (Distribution (ALE))". There you will also see the report which will trigger the idoc.
4. All the above mentioned customization is to be done by the functional consultant (or by technical after strictly seeking the permission). Once the output type is set, you go to the business application (IS-oil) which is triggering your idoc.
There, you will see the option of generating delivery (or something similar, again only the person who has worked on the application can tell that). there you can populate the idoc.
Once the idoc is populated by the application, there are couple of ways of triggering the idoc.
 a. trigger the idoc on saving the doucment. this triggers idoc as soon as you save the idoc.
 b. Collect for mass processing. For this you need to run the report RSNASTED after the idocs are populated to trigger them.
 c. Collect for application specific posting. For this , you need to know the transaction, specific to your business data to trigger the idoc and all you need to do is just run that transaction.
Hope you got the points mentioned above. Kindly go through them carefully and then give me your mail id. I will send you one good document which will clear your understanding.
Hope this was helpful.
<REMOVED BY MODERATOR>
Cheers,
Karan
Edited by: Alvaro Tejada Galindo on Apr 21, 2008 3:09 PM

Debug the Outbound IDoc

Hi,
I have a outbound IDoc.
I would like to reprocess the same and test the FM.
I am going through the Tcode :WE19.
put the IDOC : XXX in the exisiting IDoc field. Execute.
I get to see the IDoc structure and the data.Then i click on the "standard outbound processing".
I would like to get into the FM and debug it.
But once i press "standard outbound processing".
It is giving a pop up which says "start outbound processing of file immediately"
No of IDoc's to be generated.
Receiver port
Port type
output file
etc.
But i would like to get into the debug mode.
Pls advise.

Set ur Break point at your code
now come to VA02 Transaction and use order number.
click on enter
GOTO->HEADER->OUTPUT
Give the output type and print medium should be 6(EDI) or A( ALE)
Click on Further data and select->select send with periodically scheduled job and save it.
Now Come to SE38 and use RSNAST00
Output Application : V1
Object key - order Number ( 10 digit)
Output type - BA00( SAP Standard)
Transmission medium = 6(EDI) ,A(ALE)
Now it will stop at your code.
Reward Points if it is helpful
Thanks
Seshu
Message was edited by:
Seshu Maramreddy
Message was edited by:
Seshu Maramreddy

Debugging outbound idocs

Hi,
Can anyone suggest me how to debug the outbound idocs like in case we19 for inbound.
i am creating an idoc for ORDERS message type with process code ME10. i need to debug to know if data is populating in segments correctly.
shylesh

Hi Sailesh,
You can set break point at FM IDOC_OUTPUT_ORDERS and go through the code step by step.
Also you can check customer function for any custom enhancement related to populating/deleting IDoc segment within the above FM.
Hope this will help.
Regards,
Ferry Lianto

Outbound IDoc setting through ACC_GL_POSTING

Similar Messages

Maybe you are looking for