Standard Idocs or Bapis

Hi,
Are there any standard Idocs or Bapis for posting the data into transactions ME42N and IK11?
Thank You.

Hi Manju,
Thank you for the info.
my mail id is [email protected]
I am in Hyderabad.
I will try to contact you on your number.
I am not much familiar with Cross Application components.
and thanks for the help.
How do we generally get the data to be posted to the Transaction thru idoc? Is it in a flat file or something else?
Where should I give the flatfile name?
Thank you in advance.

Similar Messages

Need T code and standard IDOC or BAPI

Hi All
Need Transaction Code For Assortment Module.
Is there any Standard Idoc or Bapi for Assortment Module Conversion. Please share.
Regards
Aboli

Hi,
Below are the transactions related to Assortment
WSOA3 Assortment Display
WSOA1 Assortment Create
WSOA2 Assortment Change
WSOA6 Assortment Assignment Tool
WSO7 Display Assortment Module Assignment to Assortment
WSL5 Modules In Assortment
WSO1 Assortment Module Create
WSO5 Maintain Assortment Module assignment to Assortment
WSK1 Assortment Copy
WDBM Manual Selection Assortment List
I hope it helps you.
Thanks
Ravi kanth

Standard Idoc or BAPI to trasfer the routes and stages data

Hi guys,
We want to transfer the routes and stages data from one SAP system to other SAP system . can u suggest any standard idocs or BAPIs to do the job.
thanks
sankar
Edited by: sudhakar murthy on Apr 1, 2009 10:18 AM

hello guys
any idea on this????
thanks

Are there any standard Idocs or Bapis for posting the data into transaction

Hi,
Are there any standard Idocs or Bapis for posting the data into transactions ME42N and IK11?
Thank You.

Thank you.
Any idea of the other one?

Idocs and BAPIs

Hello,
Could you tell me please what are the standard Idocs and Standard Bapis available.
If possible could you tell me why do we use those standard Idocs and Bapis.
Thank you

Hi Jyotsna,
BAPI:
http://help.sap.com/saphelp_nw04/helpdata/en/3e/ecf226942511d2ad4b080009b0fb56/frameset.htm
or
Standard BAPI:
Look at the Transaction BAPI.
T-code: BAPI
Go to the T-Code se37 -
Type BAP* then click F4.
You can find the Standard IDOC's on T- Code in : WE60
check the below link for the list of idocs
http://www.erpgenie.com/sapedi/idoc_interface.htm
Thanks,
Satya Kumar
Reward points if it is useful.
Edited by: SATYA KUMAR AKKARABOYANA on Apr 17, 2008 2:28 PM

Standard IDOC/BAPI to create work order in CRM from ECC PS

Hello Guys,
Any input on any standard IDOC/BAPI I could use to create a work order in SAP CRM based on the data feed from SAP ECC (Project systems)?
Any help on this would be really appreciated.

Hii.
Did u get answer of SAP-> XI->CRM. IF so, share wid us.
I m stuck in same kinda scenario

Standard IDoc / BAPI to get Employee Personal Details

Hi All,
Is there any Standard IDoc / BAPI to get Employee Personal Details like EMP-ID Name, Address in HR Modules.
Bye
Satish Reddy

check with this: bapi_persdata_getdetailedlist

Standard IDocs for Inbound Sales Invoice

Hi All,
Beginner in the forum.
I have a requirement to develop an IDoc interface for Sales Invoice. I am not sure about the Basic IDoc Type, Message Type and Inbound Function Module to be used.
I can see Basic Types INVOIC02/01 and Message Type INVOIC. And the Function Modules IDOC_INPUT_INVOIC_FI and IDOC_INPUT_INVOIC_MM assigned in WE57. As my requirement is in SD perspective, I am little confused which one to use.
Any pointer would be helpful.
Thanks in Advance,
Khanshi

Sales invoices are generated referencing existing orders and deliveries through VF01 or VF04. Most if not all data for creating the invoice comes from the existing order/delivery documents (except may be freight costs etc which are know only during invoice time). So there is no standard IDoc (as most data for creating sales invoice is already there in SAP in the form of reference delivery/order) to create a Sales invoices. Sales invoices created through VF01/VF04 are outbound and can trigger INVOIC message type IDoc through IDOC_OUTPUT_INVOIC which is sent from SAP to the customer for billing purposes.
The IDOC_INPUT_INVOIC_FI and IDOC_INPUT_INVOIC_MM are for creating inbound vendor FI invoice (like that created by FB60) and MM vendor invoice (like that created by MIRO) respectively.
If you want to create a sales invoice through BAPI the below modules are available but I am sure there isn't a standard IDoc function to post a inbound INVOIC IDoc to customer/sales invoice. These BAPIs will of course require you to input the reference document (delivery or order) to create the invoice.
BAPI_BILLINGDOC_CREATE
BAPI_BILLINGDOC_CREATEFROMDATA
BAPI_BILLINGDOC_CREATEMULTIPLE
Best regards,
Vishnu Tallapragada

Data migration ALE or idocs and bapis

hi ,
thank you guys for the support.
i am into a data migration project.
i need the initial setup for the idocs and bapis.
i dont know anything about these so can u send me the process for the setup and the data migration process too with idocs and bapis.
i didnt understand when they asked me if we can data migrate with a ALE, is that the same as using idocs and bapis or is it a different approach.
u can send me at any inofrmation connected to my eamil addr.
i would really appreciate that.
thank you.

Hi,
Outbound:
Step 1. Application document is created when transaction is saved.
2. Message control is invoked.
3. Messages are processed by system.
4. Messages are Edited (if desired).
5. Output (ALE / EDI) is checked
6. Validate against Message control record from Partner Profile
7. Application Document is saved.
8. Entry NAST table is created for every selected output program
along with Medium & Timing.
9. Check for Process Immediately .
If (yes)
Determine Processing Program from TNAPR Table.
ELSE
Execute RSNASTED Program.
10. Read Partner Profile to determine Process Code.
11. Process Code points to the Function Module & Invoked.
12. IDoc is generated.
13. Check for ALE Request.
if (Yes)
Perform Filters, Conversions, Version Changes etc.
Else.
IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
3. Data in Control Record is validate against the Partner Profile.
4. IDoc is generated in Database and syntax check is carried out.
5. IDoc file is deleted once file read.
6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
7. Check for Process Immediately.
If NO
Execute RBDAPP01 Program
Else
Read Process Code from Partner Profile
Process Code Points to Function Module
Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
Just follow the procedure
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 ( )
The BAPIs Create() and CreateFromData() create an instance of an SAP business object type, for example, a purchase order. These BAPIs are class methods.
Change( )
The BAPI Change() changes an existing instance of an SAP business object type, for example, a purchase order. The BAPI Change () is an instance method.
Delete( ) and Undelete( ) The BAPI Delete() deletes an instance of an SAP business object type from the database or sets a deletion flag.
The BAPI Undelete() removes a deletion flag. These BAPIs are instance methods.
Cancel ( ) Unlike the BAPI Delete(), the BAPI Cancel() cancels an instance of a business object type. The instance to be cancelled remains in the database and an additional instance is created and this is the one that is actually canceled. The Cancel() BAPI is an instance method.
Add<subobject> ( ) and Remove<subobject> ( ) The BAPI Add<subobject> adds a subobject to an existing object inst! ance and the BAPI and Remove<subobject> removes a subobject from an object instance. These BAPIs are instance methods.
BAPI-step by step
http://www.sapgenie.com/abap/bapi/example.htm
just refer to the link below
http://www.sapmaterial.com/?gclid=CN322K28t4sCFQ-WbgodSGbK2g
list of all bapis
http://www.planetsap.com/LIST_ALL_BAPIs.htm
for BAPI's
http://www.sappoint.com/abap/bapiintro.pdf
http://www.sappoint.com/abap/bapiprg.pdf
http://www.sappoint.com/abap/bapiactx.pdf
http://www.sappoint.com/abap/bapilst.pdf
http://www.sappoint.com/abap/bapiexer.pdf
http://service.sap.com/ale
http://service.sap.com/bapi
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf
http://www.planetsap.com/Bapi_main_page.htm
http://www.topxml.com/sap/sap_idoc_xml.asp
http://www.sapdevelopment.co.uk/
http://www.sapdevelopment.co.uk/java/jco/bapi_jco.pdf
Also refer to the following links..
www.sap-img.com/bapi.htm
www.sap-img.com/abap/bapi-conventions.htm
www.planetsap.com/Bapi_main_page.htm
www.sapgenie.com/abap/bapi/index.htm
Checkout !!
http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
http://techrepublic.com.com/5100-6329-1051160.html#
Example Code
U need to give the step_nr, item_nr, cond_count and cond_type so the correct conditon will be updated. If no condition exists for the given parameters, a new condition will be created.
U can find these parameters for a particular condition type in table KONV.
*& Form saveTransactionJOCR
text
--> p1 text
<-- p2 text
FORM saveTransactionJOCR .
data: salesdocument like BAPIVBELN-VBELN,
order_header_inx like bapisdh1x,
order_header_in like bapisdh1,
return type standard table of bapiret2 with header line,
conditions_in type standard table of bapicond with header line,
conditions_inx type standard table of bapicondx with header line,
logic_switch like BAPISDLS,
step_nr like conditions_in-cond_st_no,
item_nr like conditions_in-itm_number,
cond_count like conditions_in-cond_count,
cond_type like conditions_in-cond_type.
salesdocument = wa_order_information-VBELN.
LOGIC_SWITCH-COND_HANDL = 'X'.
order_header_inx-updateflag = 'U'.
conditions
clear conditions_in[].
clear conditions_inx[].
clear: step_nr,
item_nr,
cond_count,
cond_type.
step_nr = '710'.
item_nr = '000000'.
cond_count = '01'.
cond_type = 'ZCP2'.
CONDITIONS_IN-ITM_NUMBER = item_nr.
conditions_in-cond_st_no = step_nr.
CONDITIONS_IN-COND_COUNT = cond_count.
CONDITIONS_IN-COND_TYPE = cond_type.
CONDITIONS_IN-COND_VALUE = 666.
CONDITIONS_IN-CURRENCY = 'EUR'.
append conditions_in.
CONDITIONS_INX-ITM_NUMBER = item_nr.
conditions_inx-cond_st_no = step_nr.
CONDITIONS_INX-COND_COUNT = cond_count.
CONDITIONS_INX-COND_TYPE = cond_type.
CONDITIONS_INX-UPDATEFLAG = 'U'.
CONDITIONS_INX-COND_VALUE = 'X'.
CONDITIONS_INX-CURRENCY = 'X'.
append conditions_inx.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
EXPORTING
SALESDOCUMENT = salesdocument
ORDER_HEADER_IN = order_header_in
ORDER_HEADER_INX = order_header_inx
LOGIC_SWITCH = logic_switch
TABLES
RETURN = return
CONDITIONS_IN = conditions_in
CONDITIONS_INX = conditions_inx
if return-type ne 'E'.
commit work and wait.
endif.
ENDFORM. " saveTransactionJOCR
Bdc to Bapi
The steps to be followed are :
1. Find out the relevant BAPI (BAPI_SALESORDER_CHANGE for VA02).
for VA01 use BAPI_SALESORDER_CREATEFROMDAT2
2. Create a Z program and call the BAPi (same as a Funtion module call).
2. Now, if you see this BAPi, it has
-> Importing structures.
eg: SALESDOCUMENT: this will take the Sales order header data as input.
-> Tables parameters:
eg: ORDER_ITEM_IN: this will take the line item data as input.
Note :
Only specify fields that should be changed
Select these fields by entering an X in the checkboxes
Enter a U in the UPDATEFLAG field
Always specify key fields when changing the data, including in the checkboxes
The configuration is an exception here. If this needs to be changed, you need to complete it again fully.
Maintain quantities and dates in the schedule line data
Possible UPDATEFLAGS:
U = change
D = delete
I = add
Example
1. Delete the whole order
2. Delete order items
3. Change the order
4. Change the configuration
Notes
1. Minimum entry:
You must enter the order number in the SALESDOCUMENT structure.
You must always enter key fields for changes.
You must always specify the update indicator in the ORDER_HEADER_INX.
2. Commit control:
The BAPI does not run a database Commit, which means that the application must trigger the Commit so that the changes are read to the database. To do this, use the BAPI_TRANSACTION_COMMIT BAPI.
For further details... refer to the Function Module documentation for the BAPi.
Bapi to VB(Visual Basic)
Long back I had used the following flow structure to acheive the same.
Report -> SM59 RFC destination -> COM4ABAP -> VB.exe
my report uses the rfc destination to create a COM session with com4abap. com4abap calls the vb.exe and manages the flow of data between sap and vb exe.
You need to have com4abap.exe
If com4abap is installed you will find it in sapgui installatin directory , C:\Program Files\SAPpc\sapgui\RFCSDK\com4abap.
else refer OSS note 419822 for installation of com4abap
after making the settings in com4abap to point to the vb program and setting up rfc destination in sm59 to point to com4abap session , you can use the following function modules to call the vb code.
for setting up com4abap and rfc destination please refer to the documentation for com4abap.
Invoke NEW DCOM session
call function 'BEGIN_COM_SESSION'
exporting
service_dest = service_dest "(this will be a RFC destination created in SM59)
importing
worker_dest = worker_dest
exceptions
connect_to_dcom_service_failed = 1
connect_to_dcom_worker_failed = 2
others = 3.
call function 'create_com_instance' destination worker_dest
exporting
clsid = g_c_clsid
typelib = g_c_typelib
importing
instid = g_f_oid
exceptions
communication_failure = 1 message g_f_msg
system_failure = 2 message g_f_msg
invalid_instance_id = 3
others = 4.
call function 'com_invoke' destination worker_dest
exporting
%instid = g_f_oid
%method = 'UpdatePDF'
sntemp = g_v_const_filent
snsysid = sy-sysid
snflag = 'N'
tables
rssaptable = g_t_pdfdetail1
%return = g_t_pdfdetail1 "t_test
exceptions
communication_failure = 1 message g_f_msg
system_failure = 2 message g_f_msg
invalid_instance_id = 3
others = 4.
then close the com session , using
FM delete_com_instance
FM END_COM_SESSION
Thanks and regards,
Sarada

Regarding Selection of IDOC Or BAPI

Hi All,
I have One Doubt on Choosing IDOC or BAPI
If We Have Scenario like File to R/3 .
Here I have the Standard IDOC And I have a Suitable BAPI also To Achieve this.
Then Which one I have to Select in both
Regards
Vamsi

Hi vamsi for your scenario File to R/3
you can go for file to Idoc scenario
below links will help u for this scenario , if stuck anywhere pls mail me , will solve
You can look at the following url (contains step by step approach):
http://www.****************/articles/XI/XIMainPage.htm
Following blog is step by step of File to Idoc scenario
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping File to IDoc
For more information please find the belwo links:
http://help.sap.com/saphelp_nw2004s/helpdata/en/d4/0a43a124e8924ea890cf0855860db5/frameset.htm
For any File -> XI -> IDoc scenario ref:
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
Just have a look at this link:
file to idoc scenario
Pls reward if useful

What is the standard IDOC for substation management??

hi friends..
could you please tell me standard idoc for substation management ?
and also tell me standard BAPI for substation management??
please help me..
thanks and regards
regards
ram

Hi michal..
thank you very much for your quick response.
i got source xml file like this
<?xml version="1.0" encoding="utf-8" ?>
- <MonthlyEnergies xmlns="http://aaaaa.org/MonthlyEnergy.xsd">
<Values Power_Produced="22" Reduction_Power_Consumed="1203.92" Ancillary_Power_Consumed="1056.08" UOM="KWH" Date="2006-09-30T00:00:00" />
</MonthlyEnergies>
i am trying to convert this into SAP .
for this i need IDOC .
Power_Produced = RK40C_KBXXN-STAGR (RK40C_KBXXN is structure)
Reduction_Power_Consumed = RK40C_KBXXN-STAGR
Ancillary_Power_Consumed = RK40C_KBXXN-STAGR
UOM=RK40C_KBXXN-MEINB
date = BUDAT
guide me..
thanks and regards
ram

Journal voucher IDOC or BAPI

Hi All,
We will be getting one file from external system and I need to post journal vouchers in SAP. We are discussing on posting Journal Vouchers through IDOC or BAPI. Basically we are looking at automating this process. Please let me know which IDOC and Message Type will help me in posting Journal Vouchers. Also please let me know which Standard BAPI or Functional Module will help me in Posting Journal Voucher.
Thanks
Rajanikanth

Hi All,
BAPI BAPI_ACC_GL_POSTING_POST can post an Journal Voucher.
Thanks
Rajanikanth.

Different between ALE, IDOC and BAPI?

Hi Folks,
What is the different between ALE, IDOC and BAPI? and send me the following steps?
Thanks in advance.
Siva

Hi,
please read the below lines.
ALE
ALE is SAP proprietary technology that enables data communications between two or more SAP R/3 systems and/or R/3 and external systems. When a new enterprise resource planning (ERP) solution such as R/3 is implemented, companies have to interface the ERP system with legacy systems or other ERP systems.
ALE provides intelligent mechanisms where by clients can achieve integration as well as distribution of applications and data.
ALE technology facilitates rapid application prototyping and application interface development, thus reducing implementation time.
The ALE components are inherently integrated with SAP applications and are robust, leading to a highly reliable system.
ALE comes with application distribution/integration scenarios as well as a set of tools, programs, data definitions, and methodologies that you can easily configure to get an interface up and running.
BAPI
BAPIs provide a stable, standardized method for third-party applications and components to integrate into the Business Framework. These interfaces are being specified as part of SAP's initiative with customers, partners and leading standards organizations. Also, SAP has implemented the emerging Object Application Group (OAG) specifications with BAPIs.
Pros and Cons for both BAPI and Call Transaction
BAPI
One of the big plusses for BAPIs is that the interface and function are not supposed to change. This is a big plus when you do upgrades or hot packs because the transaction can change (format, required inputs etc) which means you then need to update the call transaction.
Some of the BAPIs are better documented and easier to use than others.
You usually need to perform the BAPI that actually does the COMMIT after you call your BAPI.
The Program coding for calling a BAPI is usually cleaner than setting up the screen flow etc for the Call Transaction.
You don't need to worry about special data circumstances interrupting the normal data flow of the screens and causing errors because of that.
BAPIs probably have better performance since they don't do the screen flow processing.
In general if the BAPI exists for the transaction you want to perform and you can figure out how to use it the BAPI is probably the best way to go.
This is just from my experience working with both BAPI and Call Transaction. I have had some very good successes with BAPIs, but very occasionally found that I could not get the BAPI to perform the update I needed.
Regards,
Anki Reddy.

IDoc or BAPI to send Usage Decision to external system

Dear SAP experts,
I am searching for an IDoc or BAPI which allows me to send the Usage Decision (on a QM Inspection Lot) to an external system.
Can anyone help me with this? Please advice.
Best regards,
Kenny

I think there is no standard IDoc that can be used. But you can define (customize) a follow up action for the usage decision in R/3. This follow up action could be a Z_* program that triggers a custom IDoc. This would suit your requirements I guess!
Regards,
Kai

Standard Idocs.

Hi All ,
I'm Venkat . Can anybody tell me ,Is any standard Idocs are there for Sales Order, Purchase Order like for example MATMAS for materials master like that.
I'm waiting 4 reply.

Hi Venkat,
SALESORDER_CONFIRMDELIVERY(Message type) -> message type for Delivery Confirmation (SalesOrder)
Idoc types are:
SALESORDER_CONFIRMDELIVERY01
SALESORDER_CREATEFROMDAT201
SALESORDER_CREATEFROMDAT202
SALESORDER_CREATEFROMDAT2 -> Sales order: Create Sales Order
Idoc types are:
SALESORDER_CREATEFROMDAT201
SALESORDER_CREATEFROMDAT202
SAORDERTEST -> SALES ORDER
PURCHG -> Order Confirmation/Change
PURCONTRACT_CHANGE -> BAPI to Change a Purchase Contract
Idoc types are:
PURCONTRACT_CHANGE01
PURCONTRACT_CREATE -> BAPI to Create a Purchase Contract
Idoc types are:
PURCONTRACT_CREATE01
PURCONTRACT_GETDETAIL -> BAPI to Display Details of a Purchase Contract
Idoc types are:
PURCONTRACT_GETDETAIL01
PURSAG_CHANGE -> Change a Scheduling Agreement
Idoc types are:
PURSAG_CHANGE01
PURSAG_CREATE -> Create a Scheduling Agreement
Idoc types are:
PURSAG_CREATE01
PURSAG_GETDETAIL -> Read Out Details from Scheduling Agreement
Idoc types are:
PURSAG_GETDETAIL01
ORDERS -> Purchase Orders
Idoc types are:
ORDERS01 to ORDERS05 and ORD_ID01.
if you want other details go to WE81 , and u can search all standard Message type.
Regards,
Vijay

Standard Idocs or Bapis

Similar Messages

Maybe you are looking for