Usefull Tcode for Idoc Administration
Hello,
i'm new to IDOC.
for the daily system check, about the idoc, which are the most usefull transaction, and what i have to check in particular?
Thanks
Hi Sleep Teck,
we can use the fallowing T codes for idocs
WE05 -> iDOCs list
WE06-> Monitoring...
idoc -> Repair and check programs.
Regards,
Satish k
Similar Messages
-
Dear friends ,
can any one give me important Tcodes for IDOC & workflow
ReddyTcode list for ALE IDOC:
ALE / EDI/ IDOCS TRANSACTION CODES
Transaction Code Description
WE02 List Of All Idocs Created. (Default, Additional, EDI)
WE05 List Of Idocs Created. (Standard, Additional)
WE06 Active Monitoring For Idoc Processing.
WE07 Idoc Statistics.
WE08 Display View u201CFile Statusu201D:Overview-Path Name.
WE09 Idoc Search For Business Contents (Database).
WE10 Idoc Search For Business Contents (Archive).
WE12 Modification Of Outbound File, Triggering Inbound Processing.
WE14 Process All Selected Idocs.
WE15 Selection Program For Issuing Output.
WE16 Trigger Inbound Processing.
WE17 Trigger Status Processing.
WE18 Generate Test Status File For Outbound Idocs.
WE19 Test Tool For Idoc Processing
WE20 Partner Profile.
WE21 Ports In Idoc Processing.
WE23 Display Test Catalog Test Idoc Interface.
WE24 Maintain Table View. Direction-1.(Outbound)
WE27 Maintain Table View. Direction-2.(Inbound)
WE30 Develop Idoc Type.
WE31 Develop Idoc Segments.
WE32 View Development.
WE33 Maintain Table Views.
WE34 Change View u201CTable Of Style Ids With The Objects To Be Loadedu201D
WE40 Display System Process Code.
WE41 Display View: Logical Msg Overview. For Outbund.
WE42 Display View: Logical Msg Overview. For Inbound.
WE43 Display Status Records.
WE44 Display Partner Types
WE45 Maintenance Interface: Forwarding Inbound/EDILOGADR For Application
WE46 Global Parameter For Idoc Interface.
WE47 Status Maintenance.
WE50 Display Text For Process Code System.
WE54 Idoc Function Module For File Name
WE56 Display Status Process Code
WE57 Idoc Assignment Of FM To Log. Message And Idoc Type.
WE58 Text For Process Code Status.
WE60 Documentation For Idoc Type.
WE61 Documentation For Idoc Record Type.
WE62 Documentation For Idoc Segment Type.
WE63 Documentation For Idoc Record Types And Idoc Types (Parser).
WE64 Process Code In Idoc Inbound And Outbound.
WE70 Conversion Table For Basic Types.
WE71 Conversion Table For Extensions.
WE72 Conversion Table For Field DOCTYP.
WE73 Conversion Table For Logical Message Type.
WE81 EDI:Logical Message Type.
WE82 Message Types And Assignment To Idoc Types.
WE84 Assignment Table Between Idoc And Application Field.
ALE / EDI/ IDOCS TRANSACTION CODES
Transaction Code Description
BD10 Send Material (Matmas)
BD11 Get Material.
BD12 Send Customer.
BD13 Get Customers
BD14 Send Vendor.
BD15 Get Vendor.
BD16 Send Cost Center. (Cosmas)
BD17 Request Cost Center.
BD18 Send G/L Accounts.
BD19 Get Master Data G/L Accounts.
BD20 Inbound Processing Of Idocs Ready For Transfer.
BD21 Creating Idoc Types For Change Pointers.
BD22 Delete Change Pointers.
BD23 Serialization Using Time Stamp: Deletion Of Old Time Stamp.
BD24 Send Cost Elements.
BD25 Send Activity Type (COAMAS)
BD26 Request Activity Type
BD27 Cost Center/Activity Types: Transmit Plan Quantities And Acty Prices.
BD28 Cost Center/ Cost Elements: Send Control Records.
BD30 Material Bom Distribution. (Bommat).
BD31 Document Structure Distribution. (Bomdoc)
BD32 Plant Allocation To Material Boms Distribution.
BD33 Distribution Of Material Variants. (STTMAT)
BD34 Distribution Of Boms (BOMORD)
BD35 ALE: Send Business Process Group.
BD36 ALE: Send Business Process.
BD37 ALE: Send Business Process Price.
BD40 Generate Idocs For Serialization Group From Change Pointers.
BD41 Dispatch Of Idocs Of Serialization Group.
BD42 Check Dispatch Status Of Idocs Of Serialization Group.
BD43 Processing Inbound Idocs Of Serialization Group.
BD44 Change View u201CSerialization Groupu201D.
BD47 Dependence Between Methods.
BD48 Dependence Between Methods And Message Type.
BD50 Activate Change Pointers For Message Type.
BD51 Characteristics Of Inbound Function Module.
BD52 Determine Work Area.
BD53 Reduce Message Type.
BD54 Change View: Logical Systems
BD55 Idoc Conversion.
BD56 Maintain Idoc Segment Filters.
BD57 Link Type And Serialization Type Of Message Type.
BD58 Convert Organizational Unit.
BD59 Allocation Of Object Type.
BD60 Additional Data For Message Type.
BD61 Activate Change Pointers Generally.
BD62 Display Conversion Rule.
BD63 Transport Of Ale Tables For A Message Type.
BD64 Display Distribution Model.
BD65 Maintain Idoc Type Required Fields.
BD66 Change Idoc Fields.
BD67 Function Module For ALE/EDI Overview.
BD68 Maintain List.
BD69 Assignment Of Idoc Type To Message Type.
BD70 Cross-System Comparison Of Number Range Objects.
BD71 Attributes For Receiver Determination.
BD72 Active Events For ALE/EDI
BD73 Start Error Handling For Non-Posted Idocs.
BD75 Status Conversion With Trfc Execution.
BD77 Generate Transport Requests For Distributing ALE Customizing Data.
BD78 Monitoring Ale Customizing Data Transport
BD79 ALE IDOC Segments - Conversion Rule
BD81 Filter Objects For BAPI Parameter Filtering
BD82 Generating Partner Profile
BD83 Re-Processing Incorrect Outbound Odocs.
BD84 Re-Processing Of Idocs After ALE Input Error.
BD85 Consistency Check: Reassignment Between Two System.
BD86 ALE Consistency Check: Create Purchase Order From Sales Order.
BD87 Select Idocs
BD89 Customizing Data Modeling For Distribution Model.
BD91 Distribute All Characteristics Via ALE.
BD92 Distribute Class Via ALE: Send Direct.
BD93 Distribution Of Classification Data Via ALE.
BD95 Ale Object View
BD96 Filter Object For Receiver Determination Of Methods.
BD97 Assign RFC Destination For Synchronous Method Calls.
BD98 Consistency Check With Workflow Link
BD99 Dependencies Between Message Types.
BD100 Display Serialized Idocs. (Serialization Using Object Types)
BD101 Serialization Using Object Types: Consistency Check.
BD102 Ale: Outbound Channel Registry. -
SCM tcodes for Basis Administration Purpose
Hi
Can anyone provide me all tcodes requirde for SAP Basis Administration for SAP SCM 5.0.
ThanksHi Amit,
Go to SE93.
Use F4
Click on application hierarchy - SAP applications, Under the tree choose & expand SCM, you will find SCM Basis.
Here you can find ALL T Codes related to SCM Basis available in the particular version of SAP what ever you may may be using 4.1, 5.0 etc.
You can use this method to find T Codes in any SAP application, provided you have access.
Hope this helps.
-Sridhar- -
What is the TCODE for number change of idoc
Hi all,
can anyone help me in chnaging the number range of IDOCS in R/3 system..
what is the TCODE for that...
Thanks in advance.
Cheers,
RaghaveshHi,
Please go to transaction SNUM/SNRO and use object EDIDOC.
Select number range and change to specific number that you wish.
Hope this will help.
Regards,
Ferry Lianto -
Tcode for global idoc interface parameters
hi,
can any one say me the tcode for global idoc interface parameters.Hi,
Welcome to SDN.
check this link might help you.
tcodes for ALE
Regards,
Amit
Reward all helpful replies. -
Tcode for Infotype log in Personnel Administration
Tcode for Infotype log in Personnel Administration
Hi Santhosh
as shared by our mates,for audit trail u can check this
To track the changes in the SAP HR system we have the SAP standard report for that.
Log report: RPUAUD00
Please do the entries in the below table to activate the log report:
V_T585A
V_T585B
V_T585C
ABAP programs RSTBHIST or RSVTPROT can be used to analyze table changes
Thanks to the contrbutors -Audit Trail is used to track the record changes
http://saperphcm.blogspot.com/2010/07/audit-trail-is-used-to-track-record.html
No Worries
KG -
What is the internal processing for idocs
Dear friends this is subbu working as a abap consultant.
can any body explain the how idocs are transfered (inbound process and outbound process)1.Here out bound means sender.Inbound mens --receiver.
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.
There are two filtering in IDoc.
Segment Filtering:
Segment filtering can be achieved using T/Code BD56. Here you can suppress a whole segment irrespective of data inside it . You have to give Message Type / Sender Prrtner / Receiver Partner.
Data Filtering:
Data filtering can be done in dustribution model (BD64) where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.
Please check this link for more information.
http://help.sap.com//saphelp_470/helpdata/EN/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm
Reward points.. -
R3 settings for IDOC-IDOC scenario
Hi,
For IDOC to IDOC scenario what are the settings we have to in R3 System other than XI configuration settings.
What are setting for both sender and receiver side.
Thanks,
KishoreHi Kishore,
http://help.sap.com/saphelp_nw04/helpdata/en/18/22b800773211d396b20004ac96334b/content.htm
http://www.erpgenie.com/index.php?option=com_content&task=view&id=346&Itemid=57
http://searchsap.techtarget.com/loginMembersOnly/1,289498,sid21_gci994575,00.html?NextURL=http%3A//searchsap.techtarget.com/expert/KnowledgebaseAnswer/0%2C289625%2Csid21_gci994575%2C00.html
http://www.thespot4sap.com/Articles/SAP_ALE_Other_Concepts_Conclusion.asp
Refer this material..
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.
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.
You can directly create an iDoc using some transaction like...
Use TCODE bd10 - to Send Data
and TCODE bd11 - to Get Data
and you can check the IDoc List using TCODE we02.
As you want step by step procedure.
1. Define Logical System and Assign Logical System
TCODE sale
2. Define RFC
TCODE sm59
3. Define Port
TCODE we21
4. Define Partner Profile
TCODE we20
5. Define Distribution Model
TCODE bd64
6. Send Data
TCODE bd10
7. Get Data
TCODE bd11
8. IDoc List
TCODE we02
There are basically two types of IDOCs.
Basic IDOCs
Extended IDOCs
Idoc Components
Basic Idoc
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extension Idoc
Extending the functionality by adding more segments to existing Basic IDOCs.
Creation of IDoc
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.
Create IDOC Type
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
u can also check all these links related to idocs
http://www.allsaplinks.com/idoc_sample.html
http://www.allsaplinks.com/
http://www.sap-img.com/
http://www.sappoint.com/abap.html
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
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://expertanswercenter.techtarget.com/eac/knowledgebaseCategory/0,295197,sid63_tax296858_idx0_off50,00.html
http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358
http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm
Reward points if this helps
Regards
Pragathi. -
Hi am interested to learn about idocs can you provide me some useful links
Hi saranya srithar ,
IDoc is an Intermediate document that holds application data.
A container used to exchange data
It is independent of the complex SAP structure to store data.
It serves as the vehicle for data transfer.
IDoc Type defines the structure and format in which the data is exchanged.
It is similar to a structure in SAP
IDoc data is an instance of IDoc Type
IDoc acts as a standard SAP interface to exchange business data through ALE.
From an SAP system, an IDoc can be sent to and received from
An SAP R/3 system
An SAP R/2 system
An EDI subsystem
Any third-party application software
Segments . Idoc data is arranged in Rows, The rows make up segments of an idoc. Each segment consists of fields/segments. Fields can contain data.
These r all the t/codes which we will come across in IDocs:
TCODE TTEXT
BD10 Send Material
BD100 IDoc display object channel view
BD101 Consistency check
BD102 Outbound registry
BD103 Inbound registry
BD104 maintain tbd53
BD105 Maintain Supported Business Objects
BD11 Get Material
BD12 Send customer
BD13 Get customer
BD14 Send vendor
BD15 Open vendor
BD16 Send Cost Center
BD17 Get Cost Center
BD18 Send General Ledger Account
BD19 Get General Ledger Account
BD20 IDoc passed to application
BD21 Select change pointer
BD22 Delete change pointers
BD23 Delete serialization data
BD24 Send Cost Elements
BD25 Send Activity Type
BD26 Get Activity Type
BD27 Send cost center activity prices
BD28 Send obj/cost element control data
BD30 Distribute material object list
BD31 Distribute document object list
BD32 Distribute plant allocations(matBOM)
BD33 Distribute material variants (ALE)
BD34 Distribute order BOM
BD35 Send Business Process Groups
BD36 Send Business Processes
BD37 Send Business Process Price
BD40 Read change pointer for group
BD41 Dispatch IDocs for group
BD42 Check IDocs for group
BD43 Post IDocs for group
BD44 Assign Message Types to Serlz. Group
BD47 Dependencies between methods
BD48 Dependency method - message
BD50 Activate Change Ptrs for Mess. Type
BD51 Maintain function modules (inbound)
BD52 Activ.change pointer per chng.doc.it
BD53 Reduction of Message Types
BD54 Maintaining Logical Systems
BD55 Maintain IDoc Conversion
BD55OLD Maintain IDoc Conversion
BD56 Maintain IDoc Segment Filters
BD57 Maintain link and serialization ty.
BD58 Convert organizational units
BD59 Allocation object type -> IDoc type
BD60 Additional data for message type
BD61 Activate Change Pointers - Generally
BD62 Define Segment Conversion Rule
BD62OLD Define Segment Conversion Rule
BD63 Transport ALE Tables of Message Type
BD64 Maintenance of Distribution Model
BD65 Maintain IDoc type required fields
BD66 IDoc type field -> change doc.field
BD67 Maintain methods (inbound)
BD68 Maintain Lists
BD68OLD Maintain Lists
BD69 Assignment of Message Type to IDoc
BD70 Synchronize Number Ranges
BD71 Define FM for dependent bus. object
BD72 Activate Events
BD73 Reposting of IDocs (ALE)
BD75 Convert IDoc Status
BD77 Distribution of control data
BD78 Monitoring control data distribution
BD79 Maintain IDoc Conversion Rules
BD79OLD Maintain IDoc Conversion Rules
BD81 Filter objects parameter filtering
BD82 Generate Partner Profiles
BD83 Send IDocs after an ALE error
BD84 Post IDocs after ALE error
BD85 Consistency check for transfer
BD86 Consistency check for sales
BD87 Status Monitor for ALE Messages
BD89 Control data model. - initial screen
BD91 Send Characteristic
BD92 Send Class
BD93 Send Classification
BD95 Specify ALE object types
BD96 filter objects of receiver determin.
BD97 Assign RFC dest. to Logical Systems
BD98 Consistency Check Workflow Connectn.
BD99 Message type dependencies
WE02 Display IDoc
WE05 IDoc Lists
WE06 Active IDoc monitoring
WE07 IDoc statistics
WE08 Status File Interface
WE09 Search for IDocs by Content
WE10 Search for IDoc in Archive
WE11 Delete IDocs
WE12 Test Modified Inbound File
WE14 Test Outbound Processing
WE15 Test Outbound Processing from MC
WE16 Test Inbound File
WE17 Test Status File
WE18 Generate Status File
WE19 Test tool
WE20 Partner Profiles
WE21 Port definition
WE23 Verification of IDoc processing
WE24 DefaultValuesForOutboundParameters
WE27 DefaultValues for Inbound Parameters
WE30 IDoc Type Development
WE31 Development IDoc Segment
WE32 Development IDoc View
WE34 Object for Display of XML IDocs
WE40 IDoc Administration
WE41 Process codes, outbound
WE42 Process codes, inbound
WE43 Funct.module: Status record display
WE44 Partner Types and Checks
WE45 Forward (inbound) (V3, EDILOGADR)
WE46 Error and Status Processing
WE47 Status Maintenance
WE50 System process codes: Texts
WE51 System process codes: Change texts
WE54 FMs for changing file names
WE55 Function Module for Path Names
WE56 IDoc Administration
WE57 Assignment Messages for Appl. Objs
WE58 Status process codes: Texts
WE59 Change status process codes
WE60 Documentation for IDoc types
WE61 Documentation for IDoc record types
WE62 Documentation for segments
WE63 Documentation
WE64 Documentation message types
WE70 Conversion: Basic types
WE71 Conversion: Extensions
WE72 Conversion: IDoc types
WE73 Conversion: Logical messages
WE81 Logical message types
WE82 Assign Messages for IDoc Type
WE84 Assignment of IDoc and appl. fields
WE85 Create Rule Names
WEBU Printing Labels via Assortment List
WEDI EDI Basis
WEINBQUEUE IDoc Inbound Queue
WEKF Purchase order SAP Retail
WEL0 Forward (inbound) (EDILOGADR)
WEL1 EDI: Interface Invoice for EDILOGADR
WELI Maintain Status Groups
cheers!
gyanaraj -
hi experts ,
iam new to this group i need help from u people,
pls send me the tcodes for the following topics
- Payment transaction
- Reversal Transaction
- Credit Transfer Transactions
- Write off Transactions
- Adjustment transactions
- Clearing Transactions
- Posting of revenue (GL Summaries)
i will reward u with points
thanks in advance
regards
vishnuHi,
I am giving the list of all Transaction Codes of all modules copied from SAP itself as our friends explained above for your ready reference.
The full list of transaction codes is maintained in the tables TSTC and TSTCT. So, you can have a look via SE16 in your own SAP system as well
Tc Report Header Description
AAVN RAVRSN00 Recalculate base insurable value
ABAA SAPMA01B Unplanned depreciation
ABAD SAPMF05A Asset Retire. frm Sale w/ Customer
ABAD0 SAPMABADR Derivation: Initial Screen
ABAKN SAPLAMDP Last Retirement on Group Asset
ABAON SAPLAMDP Asset Sale Without Customer
ABAV SAPMA01B Asset Retirement by Scrapping
ABAVN SAPLAMDP Asset Retirement by Scrapping
ABAW SAPMA01B Balance sheet revaluation
ABCO SAPMA01B Adjustment Posting to Areas
ABF1 SAPMF05A Post Document
ABGF SAPMA01B Credit Memo in Year after Invoice
ABGL SAPMA01B Enter Credit Memo in Year of Invoic
ABIF SAPMA01B Investment support
ABMA SAPMA01B Manual depreciation
ABMR SAPMA01B Manual transfer of reserves
ABMW SAPLAB01 Reverse asset trans. using doc. no.
ABNA SAPMA01B Post-capitalization
ABNAN SAPLAMDP Post-Capitalization
ABNC SAPMA01B Enter post-capitalization
ABNE SAPMA01B Subsequent Revenue
ABNK SAPMA01B Subsequent Costs
ABNV SAPMSNUM Number range maint: FIAA-BELNR
ABSO SAPMA01B Miscellaneous Transactions
ABST RAABST01 Reconciliation Analysis FI-AA
ABST2 RAABST02 Reconciliation Analysis FI-AA
ABT1 SAPLAMDP_OLD Intercompany Asset Transfer
ABT1N SAPLAMDP Intercompany Asset Transfer
ABUB SAPLABUM Transfer between areas
ABUMN SAPLAMDP Transfer within Company Code
ABZE SAPMA01B Acquisition from in-house productio
ABZK SAPMF05A Acquisition from purchase w. vendor
ABZO SAPMA01B Asset acquis. autom. offset. postin
ABZON SAPLAMDP Acquis. w/Autom. Offsetting Entry
ABZP SAPMA01B Acquistion from affiliated company
ABZS SAPMA01B Enter write-up
ABZU SAPMA01B Write-up
ABZV SAPMF05A Asset Acquis. Posted w/Clearing Acc
AB01 SAPMA01B Create asset transactions
AB02 SAPLAB01 Change asset document
AB03 SAPLAB01 Display Asset Document
AB08 SAPLAB01 Reverse Line Items
ACACAD ACEPSCALLBKEDR ACE Account Assignment
ACBD ATPBD001 Display Shared Buffer: ATP Check
ACCR MENUACCR Personal Menu Volker Hofmann
ACCR01 SAPMACCR01 Create Accrual/Deferral Document
ACCR02 SAPMACCR01 Change Accrual/Deferral Document
ACCR03 SAPMACCR01 Display Accrual/Deferral Document
ACCR04 RACCRPROCESS Execute Accruals/Deferrals
ACCR05 RACCRAPPLOG Display Accruals/Deferrals Log
ACCR06 RACCRAPPLOGDEL Delete Accruals/Deferrals Log
ACCR07 RACCRREVERSAL Reverse Accruals/Deferrals
ACEC ACE_IMG Accrual Engine - IMG
ACEPP ACEPS_PERIODIC_Accrual Engine - Periodic Postings
ACEREV ACEPS_REVERSAL_Reverse Postings
ACNR SAPMSNUM No. Range Maintenance: Ext. Service
ACTL SAPLKAZB INTERNAL: Work List
AC00 MENUAC00 Service Master
AC01 SAPLBAS0 Service Master
AC02 SAPLBAS0 Service Master
AC03 SAPLBAS0 Service Master
AC04 SAPLBAS0 Service Master
AC05 RXASMD10 List Processing: Service Master
AC06 RXASMD10 List Display: Service Master
AC08 RBDSESRV Send service
AC10 RMMLCLST Class Hierarchy with Services
AD08 SAPMSD08 Enter G/L Account Posting
AD20 SAPLSD30 Search help maintenance (for IMG)
AD21 SAPMSD20 Matchcode maintenance (for IMG)
AFAB RAPOST2000 Post depreciation
AFABN RAPOST2000 Post Depreciation
AFAF RAT08400 Assets with errors
AFAMA RAVCLUST View Maint. for Deprec. Key Method
AFAMD RACSTABL View Maint. Declining-Bal. Method
AFAMH RAVCLUST Maintain Maximum Amount Method
AFAMP RACSTABL View Maint. Period Control Method
AFAMR RACSTABL View Maintenance Base Method
AFAMS RAVCLUST View Maint. Multi-Level Method
AFAMSK RAVCLUST Method: Levels in Calendar Years
AFAR RAAFAR00 Recalculate Depreciation
AFBD RABUCH20 Recreate Dep. Batch Input Session
AFBN RAFABNEW Include New Depreciation Area
AFBP RAPOST2001 Create depreciation posting log
AFWA SAPMJBRA Create Maintain Analysis Structures
AFWFL SAPMAFWCH_FL AFWCH: Filter Maintenance
AFWO1 RAFWGO_SHOWEP1 Single Records Procedure: Monitorin
AFWO2 RAFWGO_SHOWEP2 Final Results Procedure: Monitoring
AFWS SAPMAFWCH_SEGMCMaintain Segment Level Characterist
AFX_WB AFX_WORKBENCH Archiving Workbench
AIAB SAPMA15B AuC Assignment of Dist. Rule
AIAO SAPMV76A C AM Maint. list vers. gen. line it
AIAZ SAPMA15B Display Dist. Rule Allocation
AIBU SAPMA12B Transfer Asset under Const.
AIIO SAPMV76A C AM Maintain List Version AuC
AISF RJBRSVAC FX Exposure
AISFSS RJBRSVAC Single Value Analysis: FX Exposure
AISS RJBRSVAC Single Val. Analysis - Sensitivitie
AIST SAPMA12B Reverse Settlement of AuC
AJAB RAJABS00 Year-End Closing
AJRW RAJAWE00 Fiscal Year Change
AKAB SAPMWAKA List purchasing arrangements
AKE1 SAPMV13A Create Condition
AKE10 SAPMV13A Transfer Prices: Display Overhead
AKE2 SAPMV13A Change Condition
AKE3 SAPMV13A Display Condition
AKE4 SAPMV13A Copy Condition
AKE5 SAPMV13A PCA Transfer Prices: Create Prices
AKE6 SAPMV13A PCA Transfer Prices: Change Prices
AKE7 SAPMV13A PCA Transfer Prices: Display Prices
AKE8 SAPMV13A Transfer Prices: Create Overhead
AKE9 SAPMV13A Transfer Prices: Change Overhead
AKKO SAPMWAKA Promotion pur. pr. conditions
AKVA SAPMWAKA List sales arrangements
AKVK SAPMWAKA Promotion sales price conditions
ALM_01 RJBACFART2KNZ ALM: Assign CF Type to CF Indicator
ALO1 RASHLO00 Determine ASH/DOREX Relationships
AL02 RSDB0000 Database alert monitor
AL03 RSRZOLD Operating system alert monitor
AL04 RSSTAT85 Monitor call distribution
AL05 RSSTAT27 Monitor current workload
AL08 RSUSR000 Users Logged On
AL11 RSWATCH0 Display SAP Directories
AL12 RSDBBUFF Display table buffer (Exp. session)
AL13 RSTUNSHM Display Shared Memory (Expert mode)
AL15 RSHOSTLD Customize SAPOSCOL destination
AL16 RSHOST07 Local Alert Monitor for Operat.Syst
AL17 RSRZOLD Remote Alert Monitor f.Operat. Syst
AL18 RSRZOLD Local File System Monitor
AL19 RSRZOLD Remote File System Monitor
AMRP RMCPAMRP Send Stock/Requirements List
AM04 SAPMA01A Changes to Asset Classes
AM05 RACSTABL Lock Asset Class
ANHAL RAVCLUST Maintain Cutoff Value Key
ANKA RAMUST03 Directory of asset classes
ANKL AWIZ_ANKL Generate Asset Classes
ANK0 RAVCLUST Ch.-of-Depr.-Dep. Asset Class Data
ANK1 RAVCLUST Ch.-of-Depr.-Dep. Control Specif.
ANK2 RAVCLUST Ch.-of-Depr.-Dep. Allocations
ANK3 RAVCLUST Ch.-of-Depr.-Dep. Net Worth Valuat.
ANK4 RAVCLUST Ch.-of-Depr.-Dep. Insurance Data
ANVEST RAVCLUST Maintain Investment Support Measure
AOBK RACSTABL Depreciation areas/Reduction rules
AOLA RAVC0ALA Master Data Tab
AO21 RAVCLUST Screen layout for deprec. areas
AO33 RAVCLUST Net worth tax field selection
AO42 RAVCLUST Insurance field selection
AO51 RAVCLUST Leasing field selection
AO67 RACSTABL Define Transaction Type
AO68 RACSTABL Define Transaction Type
AO73 RACSTABL Define Transaction Type
AO74 RACSTABL Define Transaction Type
AO75 RACSTABL Define Transaction Type
AO76 RACSTABL Define Transaction Type
AO77 RACSTABL Define Transaction Type
AO78 RACSTABL Define Transaction Type
AO79 RACSTABL Define Transaction Type
AO80 RACSTABL Define Transaction Type
AO81 RACSTABL Define Transaction Type
AO82 RACSTABL Define Transaction Type
AO83 RACSTABL Define Transaction Type
AO88 RAVCLUST Acct.Assignmt for Investment Suppor
AO91 RACSTABL Specify field group authorization
AO92 RACSTABL Logical field groups
ARKO RVEXARIN KOBRA: Archiving
ARQ0 RAQUER01 FIAA - Ad hoc reports
ARTE RWARTREPL Replace Articles in Layout Modules
ART0 RATREE00 FIAA - Info system
AR01 RABEST_ALV01 Call Asset List
AR02 RAGITT_ALV01 Call Up Asset History Sheet
AR03 RAHAFA_ALV01 Call Up Depreciation List
AR04 RAKAFA_ALV01 Call Up Depreciation + Interest Lis
AR05 RAZUGA_ALV01 Call Up Asset Acquisition List
AR06 RAABGA_ALV01 Call Up Asset Retirement List
AR07 RAUMBU_ALV01 Call Up Asset Transfer List
AR08 RABIKA_ALV01 Call Up Depreciation Compare List
AR09 RAVERM_ALV01 Call Up Property List
AR10 RAVERS_ALV01 Call Up Insurance List
AR11 RAINZU10 Investment Grants
AR11N RAINZU10N Investment Grants
AR12 RAANLA_ALV01 Call Up Asset Directory
AR13 RAKOPL02 Call Up Prim. Cost Plan. Dep./Int.
AR14 RAMAFA_ALV01 Call Up Manual Depreciation List
AR15 RAAEND01 Changes to Master Record
AR16 RAAEND02 Changes to Asset Classes
AR17 RALEAS01 Call Up Leasing Liability List
AR18 RASIMU02 Call Up Depr.Simulation
AR19 RAHERK01 Call Up List of Origins
AR20 RAUSAG_ALV01 Retirement comparison
AR21 RAUSMQ10 Mid-quarter Alert Report
AR22 RAUSAG_ALV04 Analysis of retirment revenue
AR23 RAITAR01 Italy: Asset register
AR24 RAITAR02 Italy: Assets at 3rd party
AR25 RAGAFA_ALV01 Depreciation posted
AR26 RASOPO_ALV01 Call up special reserve list
AR27 RAKOMP_ALV01 Call up: Group asset list
AR28 RAHIST02 Call up asset history
AR29 RAAUFW01 FI-AA Manual Revaluation
AR29N RAAUFW02 Re- and New Valuation of Assets
AR30 RAWORK01 Display Worklist
AR31 RAWORK10 Edit Worklist
AR32 RABEST_ALV01 Call Create Worklist
AR32N RABEST_ALV01 Call Create Worklist
AS_AFB SAPLAS_AFB Archive File Browser
ASCC SAPLASEL Assets on My Cost Center - GUI Vers
ASEM SAPLASEL My assets
ASIM SAPLAMDP_OLD Simulation of asset posting
ASKB RAPERB00 Periodic Asset Postings
ASKBN RAPERB2000 Periodic APC Posting Run
ASMN MENUASMN Asset Master Menu
AS01 SAPLAIST Create Asset Master Record
AS02 SAPLAIST Change Asset Master Record
AS03 SAPLAIST Display Asset Master Record
AS04 SAPMA01A Asset Changes
AS05 SAPLAIST Block Asset Master Record
AS06 SAPLAIST Delete Asset Record/Mark for Delet.
AS08 SAPMSNUM Number Ranges:Asset Number
AS100 SAPMALSMEX Legacy Data Transfer using Excel
AS11 SAPLAIST Create Asset Subnumber
AS21 SAPLAIST Create Group Asset
AS22 SAPLAIST Change Group Asset
AS23 SAPLAIST Display Group Asset
AS24 SAPLAIST Create Group Asset Subnumber
AS25 SAPLAIST Block group asset
AS26 SAPLAIST Mark group asset for deletion
AS81 SAPLAIST Create Old Group Assets Data
AS82 SAPLAIST Change old group asset
AS83 SAPLAIST Display old group asset
AS84 SAPLAIST Create legacy group asset subnumber
AS91 SAPLAIST Create Old Asset
AS92 SAPLAIST Change Old Asset
AS93 SAPLAIST Display Old Asset
AS94 SAPLAIST Create Legacy Asset Subnumber
ATPS SAPLATPS ATP Check: Send Customizing
ATRA SAPMS38T ABAP Objects Runtime Analysis
AT01 SAPLAIST Create Asset Master Record (old)
AT02 SAPLAIST Change Asset Master Record (old)
AT03 SAPLAIST Display Asset Master Record (old)
AT11 SAPLAIST Create Asset Subnumber (Old)
AT21 SAPLAIST Create Group Asset (old)
AT22 SAPLAIST Change Group Asset (old)
AT23 SAPLAIST Display Group Asset (old)
AT24 SAPLAIST Create Group Asset Sub-Number (old)
AT81 SAPLAIST Create Old Group Asset (old)
AT82 SAPLAIST Change Old Group Asset (old)
AT83 SAPLAIST Display Old Group Asset (old)
AT84 SAPLAIST Display Old Group Asset Sub-No.(old
AT91 SAPLAIST Create Old Asset (old)
AT92 SAPLAIST Change Old Asset (old)
AT93 SAPLAIST Display Old Asset (old)
AT94 SAPLAIST Create Old Asset Sub-Number (old)
AUFW RAVCLUST Maintain Revaluation Measures
AUN0 RAUMFE20 FI-AA Asset Summary
AUN1 RAUMFE20 FI-AA Asset Summary
AUN10 RAUMFE20 FI-AA Asset Summary
AUN11 RAUMFE20 FI-AA Asset Summary
AUN2 RAUMFE20 FI-AA Asset Summary
AUN3 RAUMFE20 FI-AA Asset Summary
AUN4 RAUMFE20 FI-AA Asset Summary
AUN5 RAUMFE20 FI-AA Asset Summary
AUN6 RAUMFE20 FI-AA Asset Summary
AUN7 RAUMFE20 FI-AA Asset Summary
AUN8 RAUMFE20 FI-AA Asset Summary
AUN9 RAUMFE20 FI-AA Asset Summary
AUT01 AUT_CUST01 Configuration of Logging
AUT03 AUT_CUST01 Display Configuration
AUT04 AUT_CUST_DEL04 Configuration of Long Text Logs
AUT05 AUT_DEL05 Deletion of Long Texts
AUT10 AUT_REP10 Evaluation of Audit Trail
AUVA RAUNVA00 FI-AA Incomplete Assets
AWW1 SAPMAWW1 Start asset information via ALEWEB
AW01 AW01N Asset Explorer
AW01N AW01N Asset Explorer
AXPD RXPDANALYSIS Progress Tracking Evaluations
BALA MENUBALA ALE Application menu
BALD MENUBALD ALE Development
BALE MENUBALE Area Menu for Administration
BALM MENUBALM ALE Master data
BAPI SAPLSBF_BW BAPI Explorer
BAPIW SAPLSBF_BW BAPI Explorer
BAPI45 SWO_START_BAPI_BAPI Browser
BAUP RFBVALL_0 Bank Data Transfer
BA10 SAPBAL10 Subsystem Configuration
BBPS SAPMBBPS EBP Order Status Tracking
BCABA KEN_HELP_ABAP_PBC ABAP Programming
BCA0 MENUBCA0 BP: Business Partner - Applic.Cust.
BCG7 MBARCBSP Bar chart: Call model graphic
BC15 SAPMSNUM No. Range Maint.: BP_PARTNR Partner
BDA1 RSARFCEX Call RSARFCEX
BDA5 RBDSEDOC Distribute documents
BDBG SAPLBDBG Create ALE Interface for BAPI
BDBP SAPLBDBH Hierarchy maintenance of BAPI param
BDBR SAPLDX_REGISTRARegister BAPI for Data Transfer
BDBS SAPLBDMP Generate coding for mapping
BDCP SAPMSNUM Number range maintenance: ALE_CP
BDC5 RBDCUS70 Consistency of Customizing Data
BDD5 RBDCUS71 Application Consistency Check
BDFDF RBDFEFUND Request Fund
BDFDS RBDSEFUND Send fund
BDFG SAPLBDFG ALE Interfaces from Function Module
BDLR SAPLDX_REGISTRARegistration of transfer program
BDLS RBDLSMAP Convert Logical System Names
BDLSS SAPLBDLS Converting Logical System Names
BDMC RBDMCCOP Upload info structures
BDMO RBDMONI4 ALE CCMS Group Administration
BDM2 RBDMOIN8 Monitoring: IDocs in Receiving Sys.
BDM5 RBDCUS19 Technical Consistency Check
BDM6 RBDMOINF Monitor: Check input workflow
BDM7 RBDAUD01 ALE Audit: statistical analyses
BDM8 RBDSTATE ALE Audit: Sending the confirmation
BDM9 RBDAUD02 Reorganizing the audit database
BDN1 BDSFIND_1 Business Document Service: Document
BDRC SAPLBDRC ALE: Determine Recovery Objects
BDRL RBDRCOBJ ALE: Process recovery objects
BDR1 RBDRCLOG Display application log for recover
BDR2 RBDRCCLR Reorganization of recovery data
BDTP SAPLBDDISTMODELBusiness Process- Maintain Template
BDWE02 RBDSTARTWE02 Call we02
BDXA RBDCUS48 Distribution of Distribution Groups
BDXD RBDCUS47 Import of ALE Requests
BDXE RBDCUS44 Generation of ALE Requests
BDXI RBDCUS51 Model Display (Specific)
BDXJ SAPLBAL2 Maintenance of Distribution Groups
BDXK RBDCUS40 Convert CONDAT Objects in Dist.Grou
BDXL RBDCUS57 Forward ALE Requests
BDXM RBDCUS58 Analysis of Log Table
BDXN RBDCUS59 Analyze Inbound Log Table
BDXQ RBDCUS64 IMG Display of Distribution Groups
BD10 RBDSEMAT Send Material
BD100 RBDIDOCCHAN IDoc display object channel view
BD101 RBDSERCHECK Consistency check
BD11 RBDFEMAT Get Material
BD12 RBDSEDEB Send customer
BD13 RBDFEDEB Get customer
BD14 RBDSECRE Send vendor
BD15 RBDFECRE Open vendor
BD16 RBDSECOS Send Cost Center
BD17 RBDFECOS Get Cost Center
BD18 RBDSEGLM Send General Ledger Account
BD19 RBDFEGLM Get General Ledger Account
BD20 RBDAPP01 IDoc passed to application
BD21 RBDMIDOC Select change pointer
BD22 RBDCPCLR Delete change pointers
BD23 RBDSRCLR Delete serialization data
BD24 RBDSECOE Send Cost Elements
BD25 RBDSECOA Send Activity Type
BD26 RBDFECOA Get Activity Type
BD27 RBDSEACT Send cost center activity prices
BD28 RBDSECOK Send obj/cost element control data
BD30 RBDSEBOM Distribute material object list
BD31 RBDSEBMD Distribute document object list
BD32 RBDSEPAM Distribute plant allocations(matBOM
BD33 RBDSESTT Distribute material variants (ALE)
BD34 RBDSEORD Distribute order BOM
BD35 RGSALEBP Send Business Process Groups
BD36 RBDSEBPS Send Business Processes
BD37 RBDSEBPT Send Business Process Price
BD40 RBDSER01 Read change pointer for group
BD41 RBDSER02 Dispatch IDocs for group
BD42 RBDSER03 Check IDocs for group
BD43 RBDSER04 Post IDocs for group
BD53 RBDIDOCR Reduction of Message Types
BD61 RBDTBDA1 Activate Change Pointers - Generall
BD62 SAPMKCDB Define Segment Conversion Rule
BD63 RBDCUS02 Transport ALE Tables of Message Typ
BD64 SAPLBDDISTMODELMaintenance of Distribution Model
BD70 RBDCUS03 Synchronize Number Ranges
BD72 RBDEVACT Activate Events
BD73 RBDMANIN Reposting of IDocs (ALE)
BD75 RBDMOIND Convert IDoc Status
BD77 RBDTRAN1 Distribution of control data
BD78 RBDTRAN2 Monitoring control data distributio
BD79 SAPMBKCD Maintain IDoc Conversion Rules
BD82 RBDCUS15 Generate Partner Profiles
BD83 RBDAGAIN Send IDocs after an ALE error
BD84 RBDAGAI2 Post IDocs after ALE error
BD85 RBDCUS23 Consistency check for transfer
BD86 RBDCUS26 Consistency check for sales
BD87 RBDMON00 Status Monitor for ALE Messages
BD89 RBDCUS31 Control data model. - initial scree
BD91 RBDSECHR Send Characteristic
BD92 RBDSECLS Send Class
BD93 RBDSECLF Send Classification
BD97 RBDSDEST Assign RFC dest. to Logical Systems
BD98 RBDCONCH Consistency Check Workflow Connectn
BERE RFOPFI00 Business Event Repository
BERP RFOPFI01 Business Processes
BERPC RFOPFI01 Business Processes
BGMN MENUBGMN Warranty Processing
BGM1 SAPLBG00 Create Master Warranty
BGM2 SAPLBG00 Change Master Warranty
BGM3 SAPLBG00 Display Master Warranty
BGM6 SAPLBG00 Warranty Entry for Technical Object
BG00 SAPMSNUM Number Range Maintenance: BGMK_NR
BIBS SAPLEXAMPLE_ENTExamples of User Interface Design
BIBU SAPMBIBU Test Transaction User Interface
BIC RFBVBIC_0 Transfer Bank Data from BIC Databas
BKDR SAPLKCD0 Maintain transfer rules
BKDS BKD_START Sender Structure Maintenance
BMBC RVBBINCO Batch Information Cockpit
BMCC RVBCUOBJ Integrity Check for Batch Classif.
BMCHCL SAPMMCHCL Batch Class Conversion
BMC1 RVBM00LT Create Class (Class Type 'BATCH')
BMC2 RVBM00LT Change Class (Class type 'BATCH')
BMC3 RVBM00LT Display Class (Class Type 'BATCH')
BMSM RVBSTMRK Update the standard features
BMVN SAPMSNUM Number Range Maintenance: DI_JOBID
BMV0 RBMVSHOW Manage Data Transfers
BM00 MENUBM00 Batch Management
BP SAPLBUPA_DIALOGMaintain Business Partner
BPB1 BPREP001 Evaluation of Business Partner/Role
BPB2 BPREP002 Evaluation of Business Parter Data
BPB4 BPREP003 Evaluation of Partner Relationships
BPCA CHDOC_ENTRY Partner:Change Documents - Addresse
BPCD CHDOC_ENTRY Business Partner: Change Documents
BPCF RFTBPCD1 TRGP: Change Documents
BPCG RFTBPCD2 TRGP: Change Documents Addresses
BPC1 SAPMBP01 Create Business Partner
BPC2 SAPMBP01 Change Business Partner
BPC3 SAPMBP01 Display Business Partner
BPC4 SAPMBP01 Create Bus. Partner Using Reference
BPC5 SAPMBP01 Change Business Partner - Copy
BPMD RAVC0ALA Master Data Tab
BPMDCS RAVC0ALA Master Data Tab
BPMDFI RAVC0ALA Customer Company Code Master Data
BPMDGD RAVC0ALA Master Data Tab
BPMDSD RAVC0ALA Customer Company Code Master Data
BP0 SAPLBUPA_DIALOGBusiness Partner; Initial Screen
BRF BRF_SCREEN_STARBusiness Rule Framework
BRFU01 BRF_MAINTENANCEBRF: Compare SAPscript Texts
BSVV SAPMBSVW Parameterizable status workflow evn
BSVW RSBSVW01 Linkage Status Update-Workflow Even
BSV1 RBSVDISP Where-used list for transaction
BSV2 RBSVDISP Where-used list for system status
BSV3 RBSVDISP Where-used list for object type
BSV4 RBSVDISP Status Profile Overview
BS02 SAPMBSVA Maintain status profiles
BS03 SAPMBSVA Display status profiles
BS12 SAPMBSVB Maintain object types
BS13 SAPMBSVB Display object types
BS22 SAPMBSVB Maintain system status
BS23 SAPMBSVB Display system status
BS32 SAPMBSVB Maintain processes
BS33 SAPMBSVB Display processes
BUA1 BUSSTART Create contact person
BUA2 BUSSTART Change contact person
BUA3 BUSSTART Display contact person
BUBD BUSVIEWS BuPR: Applications
BUBE BUSVIEWS BuPR: Views
BUBF BUSVIEWS BuPR: Sections
BUBG BUSVIEWS BuPR: Screens
BUBH BUSVIEWS BuPR: Screen Seq. Variants
BUBI BUSVIEWS BuPR: Events
BUBJ BUSVIEWS BuPR: GUI Standard Functions
BUBK BUSVIEWS BuPR: GUI Addl Functions
BUBL BUSVIEWS BuPR:Assgn Scr.Field->Database Fiel
BUBM BUSVIEWS BuPR: Tables
BUBN BUSVIEWS BuPR: Field Groups
BUBO BUSVIEWS BuPR: Field Grouping (Criteria)
BUBP BUPRELVW BuPR: Field Grping Using Rel. Cat.
BUBQ BUPRELVW BuPR: Field Grp. Using Role Def.Cat
BUBR BUSVIEWS BP: Field Grpg Via Activity (Cust)
BUBV BUPRELDI BP: Maintenance Without Dialog
BUBW BUBFILED BP: Generate Test File (DI)
BUBX BUSVIEWS BP: Activities
BUBY BUSVIEWS BP: Field Grpg via Activity (Ctrl)
BUBZ BUSVIEWS BP: External Applications
BUB1 BUPRELCR BuPR: Create BP relationship
BUB2 BUPRELSU BuPR: Change BP relationship
BUB3 BUPRELSU BuPR: Display BP relationship
BUB4 BUPRELCR BuPR: Create BP role definition
BUB5 BUPRELSU BuPR: Change BP role definition
BUB6 BUPRELSU BuPR: Display BP role definition
BUB9 SAPMSNUM BuPR: No. range maintenance: BP rel
BUCF SAPMSNUM BP Cust: Number Ranges
BUCG BUSVIEWS BP Cust: BP Role Field Grouping
BUCH BUSVIEWS BP Cust: Field Grouping Activity
BUCJ BUSVIEWS BP Cust: Authorization Types
BUCN BUSVIEWS BP Cust: Field Grps f. Authorizatio
BUCO BUSVIEWS BP-Cust: Screen Configuration
BUCP BUSVIEWS BP-Cust: Fld.modif.exter.applicatio
BUCS BUSVIEWS BP-Cust: Notes on Roles
BUCU BUSVIEWS BP Cust: Where-Used List
BUCV BUSVIEWS BP Cust. Field Grouping Appl.Object
BUG1 BUSSTART Create Business Partner; General
BUG2 BUSSTART Change Business Partner; General
BUG3 BUSSTART Display Business Partner; General
BUG4 BUSSTART Bus. partner general deletion flag
BUI1 BUSSTART Create Inter. Party
BUI2 BUSSTART Change Prospect
BUI3 BUSSTART Display Prospect
BUMR MENUBUMR BP Relationships: Config. Menu
BUM1 BUSSTART Create Employee (BP)
BUM2 BUSSTART Change Employee (BP)
BUM3 BUSSTART Display Employee (BP)
BUNA SAPMSNUM Number Range Maint: BP_PADRNR
BUPT MENUBUPT Business Partner Configuration Menu
BUP0 BUSSTART BDT; Multiple Call (Funct. Grp BUSS
BUP1 BUSSTART Create Business Partner
BUP2 BUSSTART Change Business Partner
BUP3 BUSSTART Display Business Partner
BUSB BUSVIEWS BDT: Assign Screen Field->DB Field
BUSC BUSVIEWS BDT: Field Grouping Criteria
BUSD BUSVIEWS BDT: BP Roles
BUSE BUSVIEWS BDT: BP Role Groupings
BUSF BUSVIEWS BDT: Application Transactions
BUSG BUSVIEWS BDT: Tables
BUSH BUSVIEWS BDT: External applications
BUSI BUSVIEWS BDT: Activities
BUSJ BUSVIEWS BP Control: FuncMod. Activity (Ctrl
BUSO BUPVIEWS BP Cust: BP Cat. Field Grouping
BUSP BUSCRCNT Generate Screen Containers
BUS1 BUSVIEWS BDT: Applications
BUS10 BUSVIEWS BDT: Search Help
BUS11 BUSVIEWS BDT: Assgn BAPI Field to Field Grou
BUS2 BUSVIEWS BDT: Field Groups
BUS23 BUSVIEWS BP Tax: Data Sets
BUS3 BUSVIEWS BDT: Views
BUS4 BUSVIEWS BDT: Sections
BUS5 BUSVIEWS BDT: Screens
BUS6 BUSVIEWS BDT: Screen Sequences
BUS7 BUSVIEWS BDT: Events
BUS8 BUSVIEWS BDT: GUI Standard Functions
BUS9 BUSVIEWS BDT: GUI Additional Functions
BUTI BUPTDARK Update Without Dialog
BUTJ BUPFILED Generate Test File (DI)
BV01 SAPMF69N BAV Transfer/Securities Init. Scree
BV02 SAPMF69N BAV Transfer / Loans Initial Screen
BV03 SAPMF69N_CORE BAV Trnsfr / Real Estate Init.Scree
BV11 SAPMF69N BAV Display / Securities Init.Scree
BV12 SAPMF69N BAV Display / Loans Initial Screen
BV13 SAPMF69N_CORE BAV Display/ Real Estate Init.Scree
BWCA SAPLBW05 SAPoffice: Internet Calendar
BWOM02 BWOMSHIERDISPLABCT-CO: Displ/Check Report Row Hier
BWSP SAPLBW02 SAPoffice: WWW
BWST SAPLPSST Gener. DataSource for BW Status Obj
BW01 RGUCBIW0_PI Generate FI-SL Extract Structure
BW03 RGUCBIW1_PI Assign DataSource/Ledger
BW07 RPHASETS BW20PI: Gen. SET Hierarchies for BW
BW09 RPHALPRH BW20PI: Product Hierarchy for SAP B
BW10 RPHALGEN BW20PI: Log. Gen. Hierarchy for BW
BYPASS RFTP_GDS_BYPASSBypass for All Reservation Systems
B1B2 RPCYERK3 Create Magnetic Media files
CAAT RVFTCAAT Foreign Trade Atrium
CAA0 SAPMC27V Process instr. usage in recipes
CAA5 SAPMC27V Mass replace proc.instr. in mst.rcp
CACS CACSMENUE Commission System: Main Menu
CACS_A RKKBRPTR Access Report Tree
CACS_B RKDBAT02 Maintain Batch Variants
CACS_C SAPMKCIC Manage Comments for Commissions
CACS_D RKDREPDV Distribute Report
CACS_G RKE_CALL_VC_TKEComn Report Characteristics Groups
CACS_H SAPMKXHI Maintain hierarchy
CACS_J RKCHINOD Maintain Hierarchy Nodes
CACS_K RKDMKCIK Maintain Key Figures
CACS_M SAPMKCB9 Test Monitor Drilldown Commissions
CACS_O RKCOBTR2 Transport Reports
CACS_P RKCOBTR4 Transport Forms
CACS_Q RKCOBTR3 Import Reports from Client 000
CACS_R RKCOBTR5 Import Forms from Client 000
CACS_S RKDSTRUC Display Structure
CACS_T RKCTRTX1 Translation Tool - Drilldown
CACS_U SAPMKCB9 Convert drilldown reports
CACS_V RKES0101 Maintain Global Variable
CACS_W SAPMKCC0 Maintain Currency Translation Type
CACS_X RKDREOBE Reorganize Drilldown Reports
CACS_Y RKDREODA Reorganize Report Data
CACS_Z RKDREOFO Reorganize Forms
CACS_0 SAPMKCEE Execute Report
CACS_1 SAPMKCEE Create Report
CACS_2 SAPMKCEE Change Report
CACS_3 SAPMKCEE Display Report
CACS_4 SAPMKES1 Create Form
CACS_5 SAPMKES1 Change Form
CACS_6 SAPMKES1 Display Form
CACS_7 SAPMKEFB Maintain Authorization Obj. Present
CACS_8 SAPMKEFB Display Authorization Obj.Presentat
CAC0 MENUCAC0 Master recipe menu
CAC2 SAPLBZFC Time Sheet: Field Selection
CAC7 SAPMSNUM Number Range Maintenance: CATS
CAC8 SAPMSNUM Number Range Maintenance: CATS_INTR
CADE RCATSDEL CATS: Delete Transaction Data
CADO CATSSHOW Time Sheet: Display Data
CANM SAPMSNUM Number range maintenance: ROUTING_M
CANR SAPMSNUM Number range maintenance: ROUTING_R
CAOR CATSSHOW Display Report (Structure-Related)
CAPP CATSSHOW CATS: Object-Related Approval
CAPS RCATSC01 Approve Times: Master Data
CATA RCATSTAL Transfer to Target Components
CATC RCATSCMP Time Sheet: Time Leveling
CATI MENUCATI CATS: Cross-Application Time
CATM SAPLMLCT Selection From Time Recording
CATP MENUCATP CATS: Cross-Application Time
CATR RCATSRIF Reorganize Interface Tables
CATS MENUCATS CATS: Cross-Application Time
CATSWF RCATSB01 CATS Workflow
CATSXC RCATSXT_START_CCustomizing: CATS for Service Prov.
CATSXT RCATSXT_START_TCATS for Service Providers
CATW SAPLCATS_ITS Record Working Time
CAT2 SAPLCATS Time Sheet: Maintain Times
CAT3 SAPLCATS Time Sheet: Display Times
CAT4 RCATSA01 CATS: Approve Data
CAT5 RCATSTPS Data Transfer CATS -> PS
CAT6 RPTEXTPT Transfer External -> Time Managemen
CAT7 RCATSTCO CATS: Transfer Data to CO
CAT8 RCATSBEL Time Sheet: Document Display
CAT9 RCATSTPM Data Transfer CATS -> PM/CS
CA00 MENUCA00 Routing Menu
CA01 SAPLCPDI Create Routing
CA02 SAPLCPDI Change Routing
CA03 SAPLCPDI Display Routing
CA10 SAPLC0VL Std. Text for Task List/Order
CA11 SAPLCPDI Create Reference Operation Set
CA12 SAPLCPDI Change Reference Operation Set
CA13 SAPLCPDI Display Reference Operation Set
CA21 SAPLCPDI Create Rate Routing
CA22 SAPLCPDI Change Rate Routing
CA23 SAPLCPDI Display Rate Routing
CA31 SAPLCPDI Create Reference Rate Routing
CA32 SAPLCPDI Change Reference Rate Routing
CA33 SAPLCPDI Display Reference Rate Routing
CA51 RCPDRK00 Print Rtg/Ref.Op.Set; Fields Fixed
CA60 RMPLAN00 Changes in Routings/Ref. Op. Sets
CA61 RCPCD002 Change Documents for Routing
CA62 RCPCD003 Documents for Ref. Op. Sets
CA63 RCPCD004 Change documents for rate routings
CA64 RCPCD005 Change documents for ref. rate rtgs
CA70 SAPMC27V PRT Where-Used Lists
CA72 SAPMC27V PRT Where-used Lists: EquipTL Types
CA73 SAPMC27V Standard Networks for PRT
CA75 SAPMC27V Mass Replace PRT
CA75N CP_PRT_MASS_CHAMass Change:Production Resource/Too
CA77 SAPMC27V Bulk Replacemt PRT: Equip.TL Type
CA78 SAPMC27V PRT Mass replacemt. in libr.network
CA80 SAPMC27V Use of Work Center in Task Lists
CA81 SAPMC27V Master recipe usage and resources
CA82 SAPMC27V Where-used Lists EQUI Work Center
CA83 SAPMC27V Standard Networks for Work Center
CA85 SAPMC27V Replace Work Center in Task Lists
CA85N CP_OPR_MASS_CHAMass replacement: work center
CA86 SAPMC27V Master recipe: replace resources
CA87 SAPMC27V Mass Replace EQUI Work Center
CA88 SAPMC27V Mass replace wrk. cntr. in lib.netw
CA90 SAPMC27V Use of Ref. Op. Set in Routings
CA95 SAPMC27V Replace Ref. Op. Set in Task Lists
CA95N CP_REF_TSK_MASSMass Change:Ref.OperationSet Ref.
CA96 SAPLCPSR Update material master
CA97 SAPLCP13 Mass scheduling using mat. master
CA97N RCPMAU03 Material Master Update - New
CA98 RCPREDE2 Deletion of task lists
CBCMOD RCCBPC_0001 Maintain SCP model
CBDE RMAFRUSY PDC records with system errors
CBHR11 BUSSTART EHS-INT: Create External Person
CBHR12 BUSSTART EHS-INT: Change External Person
CBHR13 BUSSTART EHS-INT: Display External Person
CBHR21 BUSSTART EHS-INT: Create Authority
CBHR22 BUSSTART EHS-INT: Change Authority
CBHR23 BUSSTART EHS-INT: Display Authority
CBIHM2 SAPLCBIH_MP00 EHS: Edit Measurement Projects
CBIHM3 SAPLCBIH_MP00 EHS: Display Measurement Projects
CBIHT0 RCBIH_CALL_TRANEHS: RFC - PA20 HR Master Data
CBIHT1 RCBIH_CALL_TRANEHS: RFC - CBHR11 External Person
CBIHT2 RCBIH_CALL_TRANEHS: RFC - EHSBP11 Physician
CBIHT3 RCBIH_CALL_TRANEHS: RFC - EHSBP31 Health Center
CBIHT4 RCBIH_CALL_TRANEHS: RFC - PB20 Applicant Master
CBIHT5 RCBIH_CALL_TRANEHS: RFC - CBHR21 Authority
CBIHT6 RCBIH_CALL_TRANEHS: RFC - EHSBP41 Laboratory
CBIHT7 RCBIH_CALL_TRANEHS: RFC - EHSBP51 External Company
CBIH00 MENUCBIH00 Industrial Hygiene and Safety
CBIH02 SAPLCBIH_WA00 EHS: Edit Work Area
CBIH03 SAPLCBIH_WA00 EHS: Display Work Area
CBIH12 SAPLCBIH_ER00 EHS: Edit Risk Assessment
CBIH13 SAPLCBIH_ER00 EHS: Display Risk Assessment
CBIH14 SAPLCBIH_ER10 EHS: Amount Overview
CBIH42 SAPLCBIH_PT00 EHS: Edit Pattern
CBIH43 SAPLCBIH_PT00 EHS: Display Pattern
CBIH50 REHS_OBJ_STATUSEHS: Information on Permitted Statu
CBIH51 RCBIH_QUESTCATAEHS: Call Question Catalog
CBIH52 RCBIH_QUESTIONNEHS: Call General Questionnaire
CBIH72 SAPLCBIH_FA00 EHS: Change Injury/Illness Log Entr
CBIH73 SAPLCBIH_FA00 EHS: Display Inj./Illness Log Entry
CBIH82 SAPLCBIH_IA00 EHS: Change Inc./Acc. Log Entry
CBIH83 SAPLCBIH_IA00 EHS: Display Inc./Acc. Log Entry
CBIH88 SAPLCBIH_ER12 EHS: Data Transfer for Amounts
CBIH89 SAPLCBIH_IA10 EHS: Injury/Illn.Log Data Transfer
CBIH92 RMWBP00 Agent Workbench
CBMRP SAPLCBPMRP CBP requirements planning
CBP MENUCBP Constraint Based Planning Workbench
CBPV SAPBPCPV Uploading PDC messages
CBP1 RCCBP_GEN_VAR_MMRP master data download
CBP2 RCCBP_GEN_VAR_MMRP transactional data download
CBP3 RCCBP_GEN_VAR_MSOP master data download
CBP4 RCCBP_MRP_MODELStart inintialization (MRP)
CBP5 RCCBP_SOP_PLANNDisplay ext. Planning Log SOP
CBP6 RCCBP_SOP_MODELStart SOP ext. Planning Model Init
CBP7 RCCBP_SOP_MODELUpdate SOP ext. Planning
CBWAMD MENUCBWAMD Waste Management Master Data
CBWA00 MENUCBWA00 Area Menu Waste Management
CB23 SAPBPR52 Download of Master Tables for CC5
CB25 SAPBPR54 Upload Request CC5
CB32 SAPBPM31 Initial Download of Orders via CC3
CB33 SAPBPM32 Download of Master Tables via CC3
CB34 SAPBPM33 Delta Download of Orders via CC3
CB35 SAPBPM34 Upload request for CC3
CB37 SAPBPS41 Initial Download of Activities CC4
CB38 SAPBPS42 Master data download CC4
CB39 SAPBPS43 Delta download of activities CC4
CB40 SAPBPS44 Upload request for CC4
CB42 SAPBPP21 Initial Download of Orders via CC2
CB43 SAPBPP22 Transfer of master data via CC2
CB44 SAPBPP23 Delta Download of Orders via CC2
CB45 SAPBPP24 Upload request for CC2
CCAC R_CLEAR_CAC Reset Set-Get Parameter CAC
CCF1 SAPMV13B Create Message: Error Management
CCF2 SAPMV13B Change Message: Error Management
CCF3 SAPMV13B Display Message: Error Management
CCM2 SAPLCCM_CFG_CONConfiguration Control Workbench
CCR RFPM_CUST_CHECKCustomizing Check Report
CCTM TECHS_MAINTAIN Maintain Standard Variant
CCV2 SAPMV13B Change Output: Document Management
CCW1 SAPLCCWF Task-specific Workflow Customizing
CC00 MENUCC00 Engineering Change Management Menu
CC01 SAPMC29C Create Change Master
CC02 SAPMC29C Change Change Master
CC03 SAPMC29C Display Change Master
CC04 SAPLCPDMOBJECTBDisplay Product Structure
CC05 RCC00500 Change overview
CC06 RCC00800 Flip trace protocoll for user
CC07 RCC01000 Engineering Change Mgmt information
CC11 SAPLCCIN Create Material Revision Level
CC12 SAPLCCIN Change Material Revision Level
CC13 SAPLCCIN Display Material Revision Level
CC15 SAPLCCIN Change Document Revision Level
CC16 SAPLCCIN Display Document Revision Level
CC22 SAPMC29C Change Object Management Records
CC23 SAPMC29C Display Object Management Record
CC31 SAPMC29C Create Change Request
CC32 SAPMC29C Change Change Request
CC33 SAPMC29C Display Change Request
CC60 RCC00600 Browser hierarchy
CC62 RCC00602 Conversion of change packages
CC90 SAPMSNUM Number ranges for change numbers
CC92 RCCSEECM Distribute change number
CC93 SAPMSNUM Number range maintenance: TECHS
CDESK CDESK_START CAD Desktop
CEMN MENUCEMN Cost Element Accounting
CES1 SAPMGSBM Create Set (Resource Planning)
CES2 SAPMGSBM Change Set (Resource Planning)
CES3 SAPMGSBM Display Set (Resource Planning)
CES4 SAPMGSBM Delete Set (Resource Planning)
CEVF SAPMSNUM Number ranges for CAPP formulas
CEVM SAPMSNUM Number ranges for CAPP methods
CEVV SAPMSNUM Number ranges for CAPP processes
CEV1 SAPMGSGM Create value variable(res. planning
CEV2 SAPMGSGM Change value variable (res.planning
CEV3 SAPMGSGM Display value variable(res.planning
CEV4 SAPMGSGM Delete value variable (res.planning
CEWB SAPLCPRC PP: Engineering Workbench
CEWO CM_WORKBENCH CE: Structure of product folder
CE00 MENUCE00 Menu: CAPP-based calc. of std.value
CE01 SAPLCEU1 CEP: View
CE02 SAPLCEU1 CEP: Transfer
CE03 SAPLCEU1 CEP: Review
CE11 SAPMCEVF Create standard value formula
CE12 SAPMCEVF Change standard value formula
CE13 SAPMCEVF Display standard value formula
CE16 RCCEVU08 Use of CAPP elements (single-level)
CE21 SAPMCEVM Create standard value method
CE22 SAPMCEVM Change standard value method
CE23 SAPMCEVM Display standard value method
CE31 SAPMCEVV Create standard value process
CE32 SAPMCEVV Change standard value process
CE33 SAPMCEVV Display standard value process
CE41 SAPMCEVS Simulate calculation of std. values
CFC6 RCIFLOGC Configuration of CIF Application Lo
CFC9 RCIFAPS2 Target-System-Ind. Settings in CIF
CFE01 CFX_BI_TAB_TO_CExport Documents to cFolders
CFE02 CFX_BI_BOM_EXPOExport Objects to cFolders
CFGD RDELALOG Delete Application Log Entries
CFG1 RSHOWLOG Display CIF Application Log
CFG3 CIF_APPL_LOG_SEFind in Application Log
CFI01 CFX_BI_TAB_FROMImport Documents from cFolders
CFI02 CFX_BI_BOM_IMPOImport Objects from cFolders
CFM1 RIMODGEN Create Integration Model
CFM2 RIMODACT Manually Activate Integration Model
CFM3 RIMODAC2 Activate Integration Models (Bkgd)
CFM4 RIMODOUT Display Integration Models
CFM5 RIMODSRH Integration Model Object Search
CFM6 RIMODMOD Modify Integration Model
CFM7 RIMODDEL Delete Integration Model
CFNA SAPMSNUM Maintain PRT number range: FHM_CRFH
CFO3 RCIF_TCX00V Scheduling Parameters in APO CIF
CFP1 RCPTRANS Analyze and Send Changes
CFP2 RCPQUEUE Analyze and Send Changes
CFP3 RSPPMCHG CIF: PPM Transfer of Data Changes
CFP4 RSPPMDEL Delete PPM Change Pointer
CFS0 RSTRFCQR Display Serialization Channels
CF00 MENUCF00 Prod. Resources/Tools Master Menu
CF01 SAPMCFST Create Production Resource/Tool
CF02 SAPMCFST Change Production Resource/Tool
CF03 SAPMCFST Display Production Resources/Tools
CF10 RCFCO110 PRT: Use of PRT master in prod.orde
CF11 RCFCO120 PRT: Use of material in prod. order
CF12 RCFCO130 PRT: Use of document in prod. order
CF13 RCFCO140 PRT: Use of equipment in prod. orde
CF15 RCFCO112 PRT: Use of PRT master in network
CF16 RCFCO122 PRT: Use of material in network
CF17 RCFCO132 PRT: Use of document in network
CF18 RCFCO142 PRT: Use of piece of equip. in netw
CF20 RCFCO111 PRT: Use of PRT master in orders
CF21 RCFCO121 PRT: Use of material in orders
CF22 RCFCO131 PRT: Use of document in orders
CF23 RCFCO141 PRT: Use of pc. of equip. in orders
CF25 RIAUFK20 PRT: PRT Master Usage in PM Order
CF26 RIAUFK20 PRT: Material Usage in PM Orders
CF27 RIAUFK20 PRT: Document Usage in PM Orders
CF28 RIAUFK20 PRT: Equipment Usage in PM Order
CGAB SAPLC11E EHS: Edit Phrase Set - Char. Assgmt
CGAC SAPLC11E EHS: Display Phrase Set - Char. ***
CGBB RC161AW0 EHS: Initial generation of phr. set
CGBC RC1H0XLS EHS: Load XLS Macro Spec Info Syste
CGBD RCBUI004 EHS: Copy units of measurement
CGB5 SAPMSNUM EHS: No. range maint.: SAP_CLASSR
CGB6 SAPMSNUM EHS: No. range maint.: SAP_CHARCR
CGB7 RCBUI001 EHS: Char;Class;PropTree;ClientCopy
CGB8 RCBUI003 EHS: Batch conversion of AUSP; KSSK
CGB9 RC1XREG0 EHS: Conversion REG_EG -> REG_EU
CGCL2 RMWBP00 Dangerous Goods Workbench
CGCZ RC14KCMP Match Up Master Data
CGE2 RMWBP00 Packaging Workbench
CGQM RC1DATAQMIP Specify QM Interface
CGSADM SAPLC1SVC WWI and EH&S Expert Server Admin.
CG00 MENUCG00 Basic Data Environment
CG02 RMWBP00 Substance Workbench
CG02BD RMWBP00 Specification Workbench
CG05 SAPLC100 Distribute Specification
CG1B SAPLC119 Edit Phrase Sets
CG1C SAPLC119 Display Phrase Sets
CG12 SAPLC110 Edit Phrases
CG13 SAPLC110 Display Phrases
CG2A RC100TAC Create Generation Variant
CG2B SAPLC12A Edit Generation Variant
CG2C SAPLC12A Display Generation Variant
CG3A RC1EXPSR Check Source Export
CG3B RC1EXPPH Check Phrase Export
CG3C RC1EXPSU Check Specification Export
CG3D RC1EXPPT Check Property Tree Export
CG3E RC1EXPLY Check Report Template Export
CG3F RC1IMPSR Check Source Import
CG3G RC1IMPPH Check Phrase Import
CG3H RC1IMPSU Check Specification Import
CG3I RC1IMPPT Check Property Tree Import
CG3J RC1IMPRE Check Report Import
CG3K RC1IMPLY Check Report Template Import
CG3L RC1IMPBB Check Import Log
CG3Y RC1TCG3Y Download file
CG3Z RC1TCG3Z Upload file
CG31 SAPLC132 Import Phrases
CG32 SAPLC133 Import Sources
CG33 SAPLC134 Import Specifications
CG34 SAPLC13E Import Report Template
CG35 SAPLC13C Import Property Tree
CG36 RC1RIMPS Import Reports
CG37 SAPLC1L7 Edit Worklist
CG4B SAPLC1D0 Edit Cover Sheet Template
CG4C SAPLC1D0 Display Cover Sheet Template
CG4D SAPLC1D0 Edit Acknowl. of Receipt Template
CG4E SAPLC1D0 Display Acknowl. of Receipt Templat
CG42 SAPLC1D0 Edit Report Templates
CG43 SAPLC1D0 Display Report Templates
CG5A RC1AVST1 EHS: manual entry WL generation
CG5B RC1AVST2 EHS: manual entry WL generation
CG5Z SAPLC1D8 EHS: WWI server monitor
CG50 SAPLC1G0 Edit Report
CG54 SAPLC1G0 Report Information System
CG55 SAPLC1G0 Validate Report
CG56 SAPLC1G0 Release Report
CG57 SAPLC1G0 Assign Report Versions
CG58 SAPLC1G0 Set Report to Historical
CG59 RC1AVGST EHS: manual entry WL generation
CIB2 SAPBVKK2 Update CC2 PDC messages
CIB3 SAPBVKK3 Update CC3 PDC messages
CIB4 SAPBVKK4 Update CC4 PDC messages
CIB5 SAPBVKK5 Update CC5 PDC messages
CICS MENUCICS Customer Interaction Center
CIC0 SAPMCIC0 Customer Interaction Center
CIC3 RVKUSTA1 Sales Summary
CIC4 CCMARCHLOG Archiving Logging
CIC5 CCMARCHINSTR Archiving Infostore
CIC8 MENUCIC8 CIC Customizing Menu (Temporary - L
CIF MENUCIF APO Core Interface
CIPV CIBDVERB Posting PDC records
CIP2 CIBDVERB CC2: Update PDC messages
CIP3 CIBDVERB CC3: Update PDC messages
CIP4 CIBDVERB CC4: Update PDC messages
CIP5 CIBDVERB CC5: Update PDC messages
CI10 SAPPPKOM Cust: Select Techn. Param. for Comm
CI21 CIBDKAKO Communication parameters for KANBAN
CI23 CIBDKAGR Download master data for Kanban
CI25 SAPCDUP5 Upload Request in KK5
CI31 CIBDKOMM Communication parameters for PM
CI32 CIBDOPGR Init. transfer of operations for PM
CI33 CIBDSTTA Transfer of master data for PM
CI34 CIBDOPDE Delta transfer of operations for PM
CI35 SAPCDUP3 Generate Upload Request CC3
CI36 CIBDKOMM Communication parameters for PS
CI37 CIBDOPGR Init. transfer of operations for PS
CI38 CIBDSTTA Transfer of master data for PS
CI39 CIBDOPDE Delta transfer of operations for PS
CI40 SAPCDUP4 Generate Upload Request CC4
CI41 CIBDKOMM Communication parameters for PP
CI42 CIBDOPGR Init. transfer of operations for PP
CI42N CIBDOP_DOWN_PP PP-PDC: Download Operations
CI43 CIBDSTTA Transfer of master data for PP
CI44 CIBDOPDE Delta transfer of operations for PP
CI45 SAPCDUP2 Generate Upload Request CC2
CI45N CIBDCONF_REQUESGenerate Upload Request CC2
CI50 RCPIBA00 Transfer production requirements
CI51 RCPIBZ00 Transfer production commitments
CJAL RCJ_SEND_PROJECSend project
CJA1 SAPLKAZB Proj.Rel.Order Receipts: Coll.Proc.
CJA2 SAPLKAZB Proj.Rel. Order Receipts: Ind.Proc.
CJBBS1 RCNCO085 Planning Board Report Assignment
CJBBS2 RCNCO086 Structure Overview Report Asst
CJBN RBPFCPN1 Reconstruct Availability Control
CJBV BPINDX00 Activate Project Availabilty Contro
CJBW RBPFCPD1 Deactivate Project Availabilty Cntr
CJB1 SAPLKAZB Generate Settmt Rule: Coll.Proc.
CJB2 SAPLKAZB Generate Settmt Rule: Indiv.Proc.
CJCD RCJCD002 Change documents: WBS
CJCF RKAGJOBL Carry Forward Project Commitments
CJCO RBPGJA01 Carry Forward Project Budget
CJCS RCJCD001 Standard WBS
CJC1 RKPORSSET Maintenance Dialog for Stat.by Per.
CJC2 RKPORSSET Maintain Planned Status Changes
CJEA RCNCO082 Call Hierarchy Report
CJEB RKDBAT02 Background Processing; Hier.Reports
CJEC SAPMKCC0 Maintain Project Crcy Trans.Type
CJEK RCNCCP10 Copy Interfaces/Reports
CJEM SAPMKCB9 Project Reports: Test Monitor
CJEN PS_RPSCO_REBUILReconstruct: Summarized Proj.Data
CJEO RCNRCJEO Transport Reports
CJEP RKCOBTR4 Transport Forms
CJEQ RCNRCJES Import Reports from Client
CJET RKCTRTX1 Translation Tool - Drilldown
CJEV RKES0101 Maintain Global Variable
CJEX RKDREOBE Reorganize Drilldown Reports
CJEY RKDREODA Reorganize Report Data
CJEZ RKDREOFO Reorganize Forms
CJE0 SAPMKCEE Run Hierarchy Report
CJE1 SAPMKCEE Create Hierarchy Report
CJE2 SAPMKCEE Change Hierarchy Report
CJE3 SAPMKCEE Display Hierarchy Report
CJE4 SAPMKES1 Create Project Report Layout
CJE5 SAPMKES1 Change Project Report Layout
CJE6 SAPMKES1 Display Project Report Layout
CJFA RFFMRP84 Analysis of Data Trans. into PS Cas
CJFN RFFMS300 CBM Payment Converter
CJF1 SAPMKFPR Create Transfer Price Agreement
CJF2 SAPMKFPR Change Transfer Price Agreement
CJF3 SAPMKFPR Display Transfer Price Agreement
CJF4 RKFPP001 Transfer Price Agreement List
CJG1 SAPMKFPR Enter Transfer Price Allocation
CJG3 SAPMKFPR Display Transfer Price Allocation
CJG4 RKFPI001 Enter Trsfr Price Allocation: List
CJG5 SAPMKFPR Cancel Transfer Price Allocation
CJH1 PS_SUMM_INHERITReconstruct Project Inheritance
CJH2 PS_SUMM_PROTOCOProject Inheritance Log
CJIA RKPEP010 Project Actual and Commt Paymt LIs
CJIB RKPEP011 Project Plan Payment Line Items
CJIC RKPEP012 Maintain Project Settlement LIs
CJID RKPEP012 Display Project Settlement Line Itm
CJIE RKPEP012 Projects: Retirement LI Settlement
CJIF RKPEP015 Projects: Profitability Analysis LI
CJIG RKAEP000 Display PS Cash Documents
CJI1 RKPEP008 Project Budget Line Items
CJI2 RCNEP002 Budget Line Items: Document Chain
CJI3 RKPEP003 Project Actual Cost Line Items
CJI4 RKPEP004 Project Plan Cost Line Items
CJI5 RKPEP005 Project Commitment Line Items
CJI8 RKPEP008 Project Budget Line Items
CJI9 RKPEP009 Project Struct.Pld Costs Line Items
CJJ2 SAPMGPLN Change Statistical Key Figures
CJJ3 SAPMGPLN Display Statistical Key Figures
CJK2 RPNPLPLN Change Statistical Key Figures
CJK3 RPNPLPLN Display Statistical Key Figures
CJL2 KFPSDUMMY Collective Agreement
CJNO SAPMSNUM Number range maintenance: FMCJ_BELN
CJN1 SAPLKAZB Reval. ACT: Projects Ind.Pro
CJN2 SAPLKAZB Reval. ACT: Projects Col.Pro
CJO8 SAPLKAZB Overhead COMM: Projects Ind.Pro
CJO9 SAPLKAZB Overhead COMM: Projects Col.Pro
CJPN SAPMSNUM Number Range Maintenance: Proj.Item
CJPU SAPMKPU2 Execute Project Plan Adjustment
CJP1 SAPMKPU1 Create Project Plan Adjustment
CJP2 SAPMKPU1 Change Project Plan Adjustment
CJP3 SAPMKPU1 Display Project Plan Adjustment
CJP4 SAPMKPU1 Delete Project Plan Adjustment
CJR2 RPSPF100 PS: Change plan CElem/Activ. input
CJR3 RPSPF100 PS: Display plan CElem/Activ. input
CJR4 RPSPF100 PS: Change plan primary cost elemen
CJR5 RPSPF100 PS: Display plan primary cost elem.
CJR6 RPSPF100 PS: Change activity input planning
CJR7 RPSPF100 PS: Display activity input planning
CJR8 RPSPF100 PS: Change revenue type planning
CJR9 RPSPF100 PS: Display Revenue Element Plannin
CJSA RKPSEIS1 Data Transfer to SAP-EIS
CJSB RKPSEIS2 Select Key Figure and Characteristi
CJSG RKPSETG0 Generate WBS Element Group
CJSN SAPMSNUM Number Range Maintenance: Projects
CJS2 RPSPF100 PS: Change stat. key figure plannin
CJS3 RPSPF100 PS: Display stat. key fig. planning
CJS4 RPSPF100 PS: Change stat. key figure plannin
CJS5 RPSPF100 PS: Display stat. key fig. planning
CJT2 RKPEP010 Project Actual Payment Line Items
CJVC RCNCC020 Value Category Checking Program
CJV1 SAPLCJTR Create project version (simulation)
CJV2 SAPLC -
Hi All,
Please help me with documents of IDoc & RFC.
Thanks in advance.
Regards,
SreeHi,
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.
RFC and BAPI:
RFC is Remote Function Call - a function module, which can be called remotely from outside
BAPI is also a Remote enabled function module but the difference between BAPI and RFC is in BAPI there is a bussiness object attached to it which calls SAP application internally.
can you explain RFC and BAPI???
The difference between RFc and BAPI are business objects. You create business objects and those are then registered in your BOR (Business Object Repository) which can be accessed outside the SAP system by using some other applications (Non-SAP) such as VB or JAVA. in this case u only specify the business object and its method from external system in BAPI there is no direct system call. while RFC are direct system call Some BAPIs provide basic functions and can be used for most SAP business object types. These BAPIs should be implemented the same for all business object types. Standardized BAPIs are easier to use and prevent users having to deal with a number of different BAPIs. Whenever possible, a standardized BAPI must be used in preference to an individual BAPI.
RFC is the protocol used to call functions in an R/3 system by a caller external to R/3 or to call programs external to R/3 from an R/3 system. Functions can only be called via RFC, if they are tagged as RFC functions in the SAP development workbench. They are then called RFC function modules. BAPIs are complete sets of (BAPI) function modules that model a business application.
RFC is the protocol used by SAP for remote communication, that is, for communications between remote independent systems.RFC is used for communications between two independent SAP systems, or for communications between an SAP system and a non-SAP system, such as an external application. It can also be used for communications between modules on the same system.Using the RFC interfaces you can extend the functionality of R/3 applications from an external program.
An R/3 system also contains Business Application Programming Interfaces (also called Business APIs, or BAPIs), which provide a programming interface to business objects. BAPIs are a set of methods for working with and manipulating SAP business objects.Internally, BAPIs are implemented as function modules stored in the R/3 Function Builder. Each BAPI has an equivalent internally-named function module. However, you should use the BAPI and not the function module behind it, because the BAPI provides a stable, object-oriented view of R/3 applications and data. The internal function modules or even the fact that the BAPIs are implemented as function modules are not guaranteed to remain the same in future releases of R/3.
BAPI stands for Business Application Programming Interface.
It is a library of functions that are released to the public
as an interface into an existing SAP system from an external
system.
RFC is the protocol used to call functions in an R/3 system
by a caller external to R/3 or to call programs external to
R/3 from an R/3 system.
Functions can only be called via RFC, if they are tagged as
RFC functions in the SAP development workbench. They are
then called RFC function modules. BAPIs are complete sets of
(BAPI) function modules that model a business application.
When you are familiar with web developments: RFC can be
compared to HTTP and BAPIs are CGI applications.
In other words: A BAPI function is a function module that
can be called remotely using the RFC technology.
RFC and BAPIs are remote enabled function modules. They are practicly the same. A BAPI is one step further as it usually is a self contained business function, such as "Create Purchase Order", or "Change Sales Document". BAPIs interface is very well defined and documented. BAPIs can be found in the BAPI browser via transaction BAPI. RFCs are just remote enabled function modules.
BAPI stands for Business Application Programming Interface. It is a library of functions that are released to the public as an interface into an existing SAP system from an external system.
RFC is the protocol used to call functions in an R/3 system by a caller external to R/3 or to call programs external to R/3 from an R/3 system. Functions can only be called via RFC, if they are tagged as RFC functions in the SAP development workbench.
BAPIs are RFCs, the only difference is that BAPIs usually encapulate some complete business object. For example, creating a sales order, the BAPI would do all of the steps required to create a sales order.
Regards,
Shiva. -
Need all transaction codes for idocs
need all transaction codes for idocs
Hi,
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
I know how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
BAPI tcode --- BAPI.
Also:
IDOC:
IDOC ADMINISTRATION
WE09 / WE02 IDoc lists according to content. View IDocs via specific IDoc number or business application detail contained within the contents of a segment.
WE05 View IDocs
WE60 IDoc type documentation tool
WE20 Partner profile configuration. Add partner detail together with inbound and outbound relationships. We also incorporate message control on the outbound IDocs. Utilize the organizational units to trap functional errors for further processing.
BD87 Reprocess IDocs in error or waiting for action. (Both inbound and outbound in 4.6. Use BD88 in prior versions)
1.4 IDOC DEVELOPMENT
BD55 Conversion rule user exit. Link conversion rule user exit to the different system \ partner combinations.
WE19 EDI test tool. Use to test inbound Function module changes.
WE31 Segment create
WE30 Create IDoc extension type
WE82 Link Release detail to Extension IDoc Type
WE57 Assign function module to logical message and IDoc type
BAPI: BAPI, SWO1.
Transaction codes Related for IDOC Configurations
WEDI: Area Menu for IDOCs
WE02: Display IDoc
WE19: ALE Test tool
WE30: Development of IDOC Type
WE31: Development of IDOC Segment
WE41: Process Codes, Outbound
WE42: Process Codes, Inbound
WE47: Status Maintenance
WE81: Logical Message Types
WE57: Assignment Messages for Appl. Objs
SM59: RFC Destinations (Display/Maintain)
SALE: Display ALE Customizing
BD54: Maintaining Logical Systems
BD67: Maintain methods (inbound)
BD64: Maintenance of Distribution Model
BD87: Status Monitor for ALE Messages
Reward points if found helpful...
Cheers,
Chandra Sekhar. -
Need Tcode for Synchronization of SAP Useradministration with an LDAP
Hi Experts,
i am configuring the SAPR/3 4.7EE server with an LDAPserver( OID Oracle Intranet Directory server) by using the tcodes SM59,LDAP.
Now i Need the Tcode for Synchronization of SAP Useradministration with an LDAP
when i clicked on the ServerNames tab on the screen with Tcode LDAP,
i am not getting the Synchornization screen when i clicked on the Synchronization
can anyone provide me the info where i have to do the Synchronization of SAP User Administration with an LDAP?
Regds
PhaniHi Olivier
To be specific, we have an application(.Net) which uses SAP as backend and retrieves the data from SAP using RFC and BAPI's. Well everything works fine with SAP R/3(where using the connection string and SAPConnector we could establish connection and call the RFC/BAPI).
When it comes to SAP ECC we have no idea about the connection string or how to connect using SAPConnector. I knew that ECC uses a secured connection so i want to know how to connect to SAP ECC using .Net Connnector.
For the SSL could you tell me how exactly can we apply that to the above described situation?
thanks
sathish -
Process code for Idoc BANK_CREATE01 and BANK_CHANGE01
hi,
I want to create partner profile for Idoc BANK_CREATE01 and BANK_CHANGE01 standard Idocs.
But in transaction we64 , i am not finding the inbound process code for it.
So di i have to create a process code for it??
If yes , how do i create it and also the function module to be created.
kindly help.
Regards,
Loveenahi ,
To create a partner profile <b>Tcode WE20.</b>
for your inbound or outbound idocs , just add these idocs in outbound or inbound parameters . For Idoc to File or File to Idoc , it is sufficient.
before creating partner profile you have <b>to create port Tcode WE21</b>
hope this will help
regards
HONEY -
Hi Experts,
If XI is sending an IDOC to R/3. wht are the configurations steps are required at XI and R/3 side. plz list down all the TCODES that are used at both sides?
Thanks
FaisalHi Abdhul...
Config for IDOC ...
Do these configurations in R/3 and in XI...
Step for Configuration fo IDOC in R/3
SM59-rfc destination
IDX1-port
IDX2-load metadata
we05-IDoc status records
BD54-Create Partner Number
We20-Create Partner Profile
WE19-Testing IDoc Processing
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
Reward points if it is useful..
Thanks,
Satya Kumar
Edited by: SATYA KUMAR AKKARABOYANA on Mar 19, 2008 4:13 PM
Maybe you are looking for
-
For the past 2-3 months everytime I connect my iPhone or iPod touch to my laptop to update the software through itunes I have issues. I have tried download and install option and the download only option. When the progress bar gets to 100 % downloa
-
I want to put a password security on a PDF document and optimize it to be backwards-compatible to Acrobat 5.0, but am having problems. I can't optimize unless I first save the file. But after saving the secured PDF, it won't let me optimize. It tells
-
This has been an on going problem that I hope can get fixed. I went in store today. The games I wanted were finally on the videogame kiosk machine to order. Print out all the games I want. Go to the counter and none of the games work. I couldn't pre
-
Regenerate IDOC for EEWB fields
Hi All I have added a new field via EEWB and regenerated the IDOC using transaction BDFG (to ensure that the new field appears in the IDOC for population). In the new message type, I see the additional field added there. I tried testing the IDOC in W
-
Config attached: ================ This config is very simple, but the customer has not given any information regarding the hang. He says that when the hang happens he can ping the vip address and the real IP addresses but http to the vip address does