SAP IDOC ORDERS04 Doc type support ?

How do I get an update for specbuilder that has the SAP-IDOC ORDERS04 document type ?

Hello,
It is not available in B2B Document editor standards library.
SAP used to provide these on their website at http://ifr.sap.com/catalog/query.asp
However, that page was removed about a year ago. There is an article about it here
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/5520
Rgds,Ramesh

Similar Messages

IDoc types supported by ECC 6

Hi Friends,
Could you please let me know what are all IDoc types are supported by ECC 6.0?
Any documents or link would be more helpful.
Regards,
Krish

Hi Krish,
Go to Tcode: WE30 and do a F4 on the Obj. Name field this will list all the IDOC Types supported by SAP, to get more information go to WE60(you could do a F4 here too - against Basic Type) and use the IDOC Type to read the documentation for the same.
Regards,
Chen
Edited by: Chen K V on Jun 15, 2011 10:51 AM

Integration of ECC Scheduling Agreement (Doc Type LP) with SAP TM

Hello Experts,
I am trying to integrate ECC Scheduling Agreement (Doc Type LP) to create OTR in TM System. I have maintained below settings:
1. Create and Activate Control Key
2. Output determination procedure linked to LP has output type TRS0 with requirement 27 assigned.
3. Output condition record has been created
4. I have checked Business Functions are also active
I was able to transfer other Document Types like OR; RE; FD (ECC Free of Charge); SDF (ECC Subsequent Delivery - Free of Charge); Consignment Fill up and Consignment Pick up by maintaining these settings, but not able to push Scheduling Agreement LP to TM.
The output TRS0 is not appearing automatically and if I try to insert and execute this output in Scheduling agreement, Output is failing with error message: "Order is not TM-relevant"
Is there any other config or mapping or SAP Note that needs to be applied to achieve this integration? Because I believe standard integration is available for ECC Scheduling agreement (I have read in help.sap.com).
Thanks and Regards,
Vikram Bhardwaj

Hello Vikram,
You mean this documentation:http://help.sap.com/saphelp_tm81/helpdata/en/9c/787f3c0a771e57e10000000a114084/content.htm?frameset=/en/44/b0488e9c35612be10000000a155369/frameset.htm ?
I think there is talking about the integration for SCM Basis as SOS, not Order Integration.
Regards, Marcelo Lauria

Pairing of EDI ASNI X.12 Transactions set with suitalbe SAP IDoc types

Hello,
I am looking to pair the following EDI ASNI X.12 Transactions set with suitalbe SAP IDoc types, for our EDI Integration.
Can some one help me to identify which suitable IDoc type, should I use? Your help is greatly appreciated.
142
824
830
846
853
861
862
864
866
I am not sure, I am seeking the help in the righr forum -:)
Thanks in advance.
Namadev

Hi namadev
Please you can check this link.
http://www.erpgenie.com/sap/sapedi/ansi.htm#Mapping_x12_to_SAP
thanks.

Does SAP XI (PI 7.0) support streaming to support large file/Idoc

Does SAP XI (PI 7.0) support streaming to support large file/Idoc/Message Structure transfers?

AFAIK, that is possible with flat files, when you use File Content Conversion.
Check this blog: /people/sravya.talanki2/blog/2005/11/29/night-mare-processing-huge-files-in-sap-xi
Regards,
Henrique.

Release? while assigning Z Message Type to a Standard SAP IDOC Basic type

Hi Experts,
Am trying to assign a custom Message Type to a Standard SAP IDOC Basic type in WE82 transaction, but am not sure How to find the Release(last column of WE82 Tx)? Pls. let me know.
Thank you

Hello,
In case of IDOC, Go to Transaction WE30, type your IDOC name & select basic type & extension.
After that select Go to -> Header data (Shift+F7), you will Idoc header info. In the same pop-up you will find IDOC release for which version.
Regards,
Sameer

File type support by SAP XI

Hello,
I looking for table with details about file formats that support by SAP XI.
file format that support by SAP XI with adding's (like Itemfield) and formats that not support by SAP XI.
For example:
File type .CSV support by SAP XI
File type .EDI support by sap xi with Itemfield add in
Thank you in advance for your help
Elad

XI talks with files using its File Adapter. This file adapter can pick up any file with any structure.
After picking up the file, the task of adapter is to convert it into XI readable XML format. For this,
- XI could directly understand input xml file or
- XI could read text file using file content conversion or
- u could write ur own code to read structures of any other file
So no limitations as such.
Regards,
Prateek

SAP 1099 - not showing credit memo - KG doc type

Hello,
When i run the generic w/h report for 1099, it is not showing credit memo , KG doc type .
The vendor is flagged for 1099 and also the KG doc contains the W/H base and tax code .
please let me know .
thanks very much.

Hi,
I am sorry, the note is not releasead yet. I will let you know when it would be.
Meanwhile, please check if the hints below resolves your issue:
Please run the S_P00_07000134 report (RFIDDYYWT ) with option of 'Further Selection' 'Credit Memo Doc. types' Technical name of P_CMDCTY with value of KG then desired result will show.
with Additionally
please refer the note no 945664
MANUAL ACTIVITIES:
1. Goto trasaction se38
2. Give the program name as 'RFIDYYWT'
3. Click on Goto->Text Elements->Selection Texts on the Menu bar
4. Goto editable mode.
5. Search for parameter 'P_CMDCTY'. Specify the selection text as
'Credit Memo Doc. types'. Uncheck the adjoining checkbox for Dictionary
ref.
6. Activate the changes.
I hope it helps.
Best Regards,
Vanessa Barth.

SAP IDOC

Hi All,
I have few questions on SAP IDOC's
1. If we are using Standard IDOC, then is it only the config or any coding is required to populate the IDOC. Examaple Order03
2. If we Customize, then only customize fields needs to be populated or all the fields (SAP Standard and Custom fields)
Thanks & Regards
SM

Hi
1.. If we are using Standard IDOC, then is it only the config or any coding is required to populate the IDOC. Examaple Order03
Have to do complete configuration in the system.if required very less code in the fun module can be written.
see the below doc
2. If we Customize, then only customize fields needs to be populated or all the fields (SAP Standard and Custom fields)
Only code has to be written for the population of the custome fields in the custom segments of the Idoc extension in the user exit of the idoc.
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.
<b>Reward points for useful Answers</b>
Regards
Anji
Message was edited by:
Anji Reddy Vangala

Billing doc types

Hi Gurus,
Can I confirm that invoice list is not a billing doc type and
Returns and External transactions are also not billing doc types.
I am not sure if only 'returns' is mentioned, does it mean the Returns order , the Returns delivery or credit memo request of that return or the credit memo for the returns.
thanks.
M Russo

Yes it is true that you can consider Invoice List also as one of the billing document type. I hope you would be aware of the functionality of Invoice List.
For more details, go through these documentations.
[Creating an Invoice List|http://help.sap.com/saphelp_45b/helpdata/en/dd/56111c545a11d1a7020000e829fd11/frameset.htm]
[Invoice List|http://help.sap.com/saphelp_46c/helpdata/en/dd/561102545a11d1a7020000e829fd11/content.htm]
thanks
G. Lakshmipathi

WRP1 excluding open POs based on doc type

Hi friends,
We are using SAP IS Retail ECC 6.0
In our business, we are having requirement that Open PO quantity of particular document type (eg ZNBA) should be excluded from the WRP1 requirement calculation.
Eg:
For an article 100001, Site A001, following are the details,
Reorder point - 10
Target stock - 20
Current stock - 5
Open PO quantity: (ZPO1 and ZPO2 are PO doc. types)
ZPO1 - 2
ZPO2 - 1
Now WRP gives requirement of article as of 12 quantities.
My requirement is to it should not include ZPO1 open quantity in consideration but should take ZPO2 into consideration.
Hence requirement is to create PO for 14 quantities
How do I achieve this?
We have a control in SAP IS Retail where we can specify, that stock of which storage location should be considered in replenishment requirment calculation.
Do we have a similar control for the PO Doc type? If not, how do I achieve workaround?
Thank you,
regards,
Gaurav

Hi,
Do the Following, Create a new storage location., "ZL01"
Whenever your creating a PO with this "ZPO1" document type assin this Slocation "ZL01", then do the below settings in SPRO..
SPRO->Materials Management->Consumption-based Planning->Planning->Define Storage Location MRP per plant.
(In RP indicatior please give "1"Storage location stock excluded from RP, this will exclude the stk from this location)
Regards
GK.
Edited by: Gnana Kumar on Oct 22, 2010 11:15 AM

Creation of Excise Invoice in J1IS Transaction - using DLFC ref. doc. type

Hi,
I tried to create the excise Invoice using Ref. Doc Type DLFC in J1IS by giving the material document. But it is not allowing me to process further.
The business process requirment is to create a Supplementary Excise Invoice(Customer is Billed for a lesser value earlier)
we tried the following:
1. Credit memo request
2. Credit Memo
3. Excise Invoice in J1IS using sub.Tran Type(to map the Sales exc Inv Accounts). The reson why we used J1IS is to meet the requiremnt of generating the Outgoing Excise Invoice Number which is not possible in J1IH.
Now the issue is, the excise invoice created in J1IS is not available for Utilizaton in J2IUN
Please Suggest what process to be followed to address the issue.
regards,
Girish

In normal circumstances, it is not possible to generate an excise invoice for credit / debit notes in SAP. Moreover, DLFC excise invoice type can be generated only if delivery is involved. So in order to achieve the requirement (and fool the system :-|), you can try by creating a delivery with an item category as TAX so that it will not check for stock, do PGI and invoice (credit memo) can be generated referencing credit memo request. Finally, try to generate an excise invoice via J1IIN
I have never tried this option and hence, its only a guess that this should work. Update after testing.
thanks
G. Lakshmipathi
Edited by: Lakshmipathi on Jul 26, 2011 2:07 PM

Error while trying to post inbound idoc of message type COND_A

Hi,
I am getting error while trying to post inbound idoc of message type COND_A.
If I left Usage & Condition field of segment E1KOMG then 'Table not available' idoc message is coming
and if providing value in above fields then dump is coming.
How to solve ?
Plz do reply
Thanks
Mohit

I do not see any reason why you would need to use COND_A04 if COND_A01 is working.
What if you could get COND_A04 to post and you would face the same result as in COND_A01?
If SAP does not check wrong values, then you have to do it yourself, or you report an incident at SAP (after you have searched for OSS notes that may have fixed this error already)
For example OSS Note 1169998 - IDoc: KONP-LIFNR values not checked
fixed a situation where the vendor number was not validated.

Posting of cross company transaction with different doc types

Hi,
The scenario is:-
We have two companies X and Y.
X makes a payment to Y with the following FI entries:-
Company Code X
Dr Vendor Y
Cr Bank HDFC
Company Code Y
Dr Bank ICICI
Cr Customer X
Now this needs to be a cross company transaction where the doc type for CC X should be vendor Payment 'KZ' while the doc type for CC Y should be a customer reciept with doc type 'DZ'.
Although I am able to map the accounts in cross company code config I am not able to split the transaction of different company codes with different document types.
Is there any way we can do this in standard SAP?
Thanks in advance,
Nitish

Hi
As per your issue ...There are no possibilities to post in sap with different document types.
If you want you can post cross company code transactions with one document types
Regards
vamsi

Change the backend doc type from PR to PO in BADI BBP_TARGET_OBJECTS.

Hi,
We have followed below approach for backend document type determination.
1. A custom function module contains the logic to determine the backend document type of a Shopping cart line item. THis function module, performs many checks and hence cannot be called in any BADI that is executed in Foreground.
2. I am using BADI BBP_TARGET_OBJECTS to change the follow document type by calling the custom function module.
Issue here is, if the backend document type of a line item is Purchase requisition (2) by SAP standard, and if I try to change it to Purchase order, it gives run time error and ends up in creation of Purchase order.
After further investigation I found that this line item (with default backend doc type as 2) has a desired vendor. If we change the desired vendor of this line item to fixed(To Partner function 19 from partner function 39), it allows us to change the doc type from Purchase requisition to purcahse order in BADI BBP_TARGET_OBJECTS.
But changing the partner function is possible only in BBP_DOC_CHANGE BADI, and I cannot call the custom function module there, as it may impact the performance.
Is there any other way, I can change the partner function in any of the BADIs called in background?
Or Is there any way by which I can change the backend document type from PR to PO in BBP_TARGET_OBJECTS?

Hi Parab
if you swaping 39 to 19 viadoc change badi
REQUESTER has a control on Purchase ORDER Vendor and BUYER lost a control so your business has to decide.In this case procurement department lost their control.
Fixed vendors are like inforecord and contract negotiated for best price ..
Muthu

SAP IDOC ORDERS04 Doc type support ?

Similar Messages

Maybe you are looking for