Billing output to IDoc & reprocess the IDoc in same sys. to post FI entry
I have a requirement to send the billing output to IDoc, read the same IDoc to post a FI entry but to another company code. Please suggest how can this be acheived, and is there any other alternative to acheive the above requirement.
Thanks in advance.
Hi Naga,
I have to select the records in JDBC based on different conditions each time. For example I have to select based on company code '1000' and Employee claasification 'E1' and date range. After I post these records in SAP again I want to select other records for some other company code '2000' and different business area and different dates. Basically I want to extract data multiple times based on different conditions.
-->
Such requirements cant be handle through select query of the sender...but you can handle this in the message mapping area.....you can fire a select query in the database to pick up records in a batch of 10K (do not keep any condition on this except for sorting). After the records come into PI you can send the message to your target based on the unique combination of "Company code+ Employee clasification + date range" handling this in the message mapping.
Another question is in the JDBC to IDOC scenario since the sender adapter is JDBC and the sender adapter polls depending on the duration of time ( say 60 secs ) in the adapter once after I extract the data based on a condition how do I control in such a way that the same data is not extracted again.
You can use the N--> C logic
The data records that you pick have a corresponding control table i assume. There should be a field STATUS where the initial status of record should be N.
After you pick the records this status should be made C so that only those records present in the database with status = N are picked up.
Mention the condition Status = N in the select query.
Thanks
Dhwani
Similar Messages
-
Hi,
I am devloping one report which will display some idocs.My requirnment is to reprocess (like BD87) those idoc which are there in error state.So is there any function module or program which i can call in report to reprocess the idoc?Or is there any alternative way to perform the same operation.Check out function module IDOC_INPUT, which is pretty neat. Specify the IDocs that you want to process in table parameter UNPROCESSED_IDOCS and ignore the other tables parameters IDOC_DATA and IDOC_CONTROL (can be empty when calling the function).
Cheers, harald
p.s.: Problems with reports other than BD87 is that they usually only handle a specific set of IDoc status values (e.g. RBDAPP01 is only for unprocessed IDocs in status 64 or 66, RBDMANI2 for failed IDocs in status 51, RBDAGAIE for edited IDocs in status 69, etc.) - that's why I prefer to use the function module. -
hi ,
i am not able to reprocess the idoc when the satus is 62 on the inbound side....
how to reprocess the idoc.
what is the program to reprocess the idoc....hi shyam,
u can first test the inbound idoc using we19, which is a testing tool. To reprocess an idoc u have to go to BD87.
first of all check status code of the idoc at different stages. so that u can track the problem.
Regards...
Arun.
Reward points if useful. -
Billing output by mail changing the subject line
HI,
i am sending the billing output by email, but the subject of the email getting changed regularly. my requirement is i have to set standard subject for all billing output by mail.
Reagrds
Muthuraman.DGo to Tcode - NACE - Choose V3 - Choose 'output types' on the application toolbar
- select output type - 'double click on mail and texts' at left hand side. See if you can add anything there and checck the mail. -
Flat-Idocs via the IDOC-adapter
Hi All,
I want to send a flat-IDOC via the IDOC Adapter to a SAP R/3 system. The IDOC adapter does not accept flat-IDOC, but wants xml-IDOC. Does anyone know how to send this flat-IDOC to the SAP R/3 via ALE, but without XML-lizing the IDOC?
I am looking in to the principle of tunneling, but that will involve some ABAP coding.
Cheers,
FrankHi Bhavesh,
I tried, but the IDOC adapter wants XML. The receiver IDOC adapter checks the type of the payload and determines if IDOC tunneling is used or not. I don't know yet how to change the type of the payload:
<i>method CL_IDX_IDOC_SERVICE-GET_PAYLOAD, part of package SIDOC_ADAPTER
test if idoc is in tunnel-payload-format
l_content_type = l_payload->getcontenttype( ).
IF l_content_type = if_xms_resource=>mimetype_idoc.
l_idoc_resource ?= l_payload->getdata( ).
l_tunnel_flag = 'X'.
ELSE.</i>
and with tunneling the idoc must be stored in certain tables where the receiver idoc adapter will get the IDOC instead of the payload. And our flat-idoc is in the actual payload. So the direction I am looking into is an abap mapping, which will change the payload type and stores the flat idoc in these tables, so the idoc adapter is "fooled" to believe it is IDOC tunneling.
Cheers,
Frank -
Reprocess the IDOC without using BD87
Can I reprocess an idoc through a zreport in the background. can i use the program behind BD87 and use a submit statement?
But BD87 genertes an output from which you have pick your idoc and reprocess it manually.
Thanks,
krishna.hi ,
See the status of the record and process the below program using Submit report by passing Idoc number
Program RBDMANI2 for status 51 & 52
Program RBDAPP01 for status 64 ,66
Program RBDAGAIE for status 32 and 69 (Edited IDocs)
Program RBDSYNER for status 26
Program RSEOUT00 for status 30
re-process IDocs failing in 29 status, use program RBDAGAIN.
Prabhudas -
IDOC - Delete unwanted segments and reprocess the IDOC by WE19
HI all,
I have an issue and wanted your help at this point of time.
Case - Assume that an Idoc has been rejected by system due to few bad segments. Later i dentfied that in the Idoc few segments were bad and rest are good.
If i use transaction WE19 for copying the Idoc and during selection of the segment if i delete the bad segments and copy the rest which are good. Will the Idoc be processed sucessfully with a new Idoc number so that the Bad segments i will fix it up manually in ERP. Kindly suggest. If possible let me know if any implication behind that or anything you like to add in the process to help me out.
Kindly advice me.
Regards,
Pratap
Edited by: pratap kumar on Dec 20, 2007 5:02 AMHi Pratap,
Which Idoc did you process. For each message type certain segments are Mandatory.
for example in WPUBON01 -->following segments are mandatory
Control Record --- Message type / Partner Type / Port / Server ID etc.....
E1WPB01 --- Date / Time / Partner Number etc...
E1WPB02 --- Article type / Article Number / Quantity etc...
E1WPB03 --- Condition Type / Amount etc...
E1WPB06 --- Payment method / Total Amount / card number etc...
In control record we will have the port / System ID etc.
If other segments are not there leave it....it will process successfully.....
To find out error segment refer Table EDID4 and correct the segment and post it.
Regards,
ManiKumaar -
Split the IDOC into multiple IDOC if the IDOC has more than 500 records
Hi All,
I developed an outbound IDOC in which we are facing an issue.
There is some limitation on the maximum idoc size it can handle.
If number of records is more than 500, split the idoc into multiple iDoc's, e.g. if it would have 1300 records , the result would be 2 iDoc's with 500 records, and the last one would have 300 records
How can i acheive this.
Regards
JaiHi,
1) first you need to know which message type/Idoc type you are triggering.
2) Get the Corresponding processcode from Partner profiles(WE20/ WE41).
3) Then the look for prper user-exit in the related processing FM.
4) write logic to split the IDoc accordingly.
if no proper user exit available then copy the standard processing FM and need to all ALE related configurations.
Catch hold any ABAP expert in your team to do all these.
Suresh -
Idoc reprocessing in Custom program
I have a custom program which displays the IDoc data for the message type = ZSTLSP in the ALV format.
Requiremt is that I shall select a record and change one of the coulmn contents . A button 'Reprocess' will be
made available , when clicked it needs to reprocess the Idoc . The reprocessed idoc will be strored with the new values entered
and the original idoc will be stored with status 70.
Kindly let me know how to reporcess the IDoc in the custom program.
p.s.: Function module IDOC_INPUT does also reprocess ..but it does not disoplays the updated status.Hello,
You may call standard program RBDAPP01 to reprocess the IDOCs using SUBMIT statement. Pass the IDOC Number, Message type etc. while submitting the program.
Thanks,
Venu -
IDOC reprocessing with new conversion rules
Hi All,
we've created IDOCs and after the creation the conversion rules are changed. Now we want to reprocess the IDOC's and in the reprocessing we want to use the new conversion rules.
I've tried just reprocessing, I also tried WE19, but with these 2 the conversion rules seem to left untouched.
Has anyone a solution were I can reprocess making use of the new rules?
kind regards,
PieterHi,
I've debugged the reprocessing of the idoc and it seems indeed I had to change the status, however not all statusses result in reprocessing of the rules. Status '29' Error in ALE Service works. So my problem is solved.
Thank you.
kind regards,
Pieter -
Hi,
I have a problem with idoc reprocessing .An idoc contains the date field which shows the system date.I t always shows the default system date as Thursday.
But when we reprocess some idocs ...they are not showing the default system date (Thurs day) showing the current date .
Pls advice.
Regards,
Somenathhi
use
report RBDAPP01
to change status from 51(application document not posted)
to 53(application document posted)
reward for use ful points
regards
Nagesh.Paruchuri -
hello
i need to reprocess idocs in status 03 through bd87
but it is not allowing
please helpHi Manu,
Looks like you are trying to reprocess the IDOC which is already processed correctly.
Unfortunately there is no way by which you can do it.
I can give you a work around though:
1) Go to WE19 enter your IDOC number which already has status 03 and execute.
2) On next screen it will display the IDOC, choose approporate button on toolbar (standard Function Module) to process it.
3) This will generate the new IDOC similar to the one which was posted completely.
4) Now the new IDOC should have status ready (Unless you have clicked Process Immediately in WE21 for this message type, it shud be execute by Background Job).
This approch is applicable for testing.
Let me know if it solves your query.
Regards
Shital -
Create IDOC when the credit memo is generated
I want to create an IDOC.
The IDOC will be created when the credit memo is generated.
Please help me to create the segments.
Title was edited by:
Alvaro Tejada GalindoHi
First you find the relative Idoc Type and Message type for that credit memo in the tables EDBAS and EDMSG
Then go to WE31 and create the additional segments as per your requirements apart from doing lot of other related settings
see the doc
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
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
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
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
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
>>>> SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
Regards
Anji -
Hi Gurus,
I have a problem wiht IDOCs. One of my End User is reporcessing IDOC of other country. When I look into his authorizations, he don't have authorization for that particular country where he is reprocessing. Even when I asked user, he don't know what exactly going on, but in reports system is howing user id.
If any one have any idea how it is allowing user to repocess pl let me know.
Regards
Jayakar ReddyBD87 - is used to reprocess the Idocs.
-
I have developed a File to IDOC interface in PI/XI. The file I pick up will contain a list of invoices from a vendor system ,
that I convert into ACLPAY IDOCs and post invoices.
When the IDOCs are posted into our SAP system some of the IDOCs fail and some of them are successful.
At the end of a business day the user will execute txn we05 to see the status of the IDOCs that came in for that day.
If any of the IDOCs failed the user would use WE19 to correct the data and reprocess the IDOC again.
The problem is the old IDOC that came in still has a error status and the new IDOC created by modifying the old IDOC doesnu2019t have any reference to the older IDOC.
Is there a way to see if and IDOC was created by reprocessing an already existing IDOC?
Or is there a better method to handle my scenario?
Thanks
SivaHi siva,
there are different programs and t-codes available to reprocess the error Idocs
with out creating new idocs.
Program RBDMANI2 for status 51 & 52
Program RBDAPP01 for status 64 ,66
Program RBDAGAIE for status 32 and 69 (Edited IDocs)
Program RBDSYNER for status 26
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC - Creating IDoc Type from Change Pointers
RSEOUT00 - Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
Program RSEOUT00 for status 30
re-process IDocs failing in 29 status, use program RBDAGAIN.
transactions WEINBQUEUE and WEOUTQUEUE to control the individual queues
Prabhudas
Maybe you are looking for
-
Hi Friends, If we use PNP as LDB, we will use get pernr. In the same wave if we use PNPC as LDB, which fields we need to take. If any one is having sample program using PNPC, please post to me and also pls explain how is PNPC useful Thanks in Advance
-
Repository Creation Utility Download
Hi All, As a part of Oracle Fusion Middleware installation, I am unable to find the download for Oracle Repository Creation Utiliity. Could you guide me to the right link? Regards, Balaji A
-
JDBC receiver error:ORA-06550: line 1, column 7: PL/SQL
Hi, I am geting this error in JDBC Receiver adapter. when i call the stored procedure. Last week it works fine.But i today i faced this error. Error Unable to execute statement for table or stored procedure. 'spec_utilities.SP_DELETE(Structure 'unas
-
I want to run "SAP" on my PC - where to start?
Hello, I'm seeking a career at a company that has "knowledge of SAP" as one of their requirements - this is for a position in Finance. I've watched some tutorials on SAP, specifically the "FI/CO" features - and thought that I would give it a try by i
-
Photoshop premiere Elements 12 Facebook sharing is not working
Photoshop Premiere Elements 12 Facebook Sharing is not working.