ALE Scenario using BAPI

Can anyone plz send me a sample scenario on ALE using BAPIs.
It will be still helpful if the scenario is from HR module.
Thanks,
Srinu.

Hi,
Please check this link on how BAPI works with ALE.
http://help.sap.com/saphelp_nw04/helpdata/en/4c/4c0eb7725311d396a80004ac96334b/frameset.htm
Hope this will help to start with.
rewards if it helps u
vijay pawar

Similar Messages

ALEAUD to sending system in ALE scenario using XI

Hi,
I have a quite simple ALE scenario with following components;
SAP IS/OIL -> (CREMAS) -> XI -> (CREMAS) -> SAP Retail
I have read both how-to-guides; IDOC-XI scenarios and handle ack. for IDOCs.
By activating the runtime paramter ACK_SYSTEM_FAILURE, XI will send ALEAUD in case of error on XI - this works in a way.
By using program RBDSTATE on SAP Retail - this works in a way.
Challenge 1:
In case of error on XI, the ALEAUD message sent back to IS/OIL doesn't contain neither message type or the referenced IDOC from IS/OIL;
E1ADHDR-MESTYP
E1ADHDR-MESTYP_LNG
E1STATE-DOCNUM
is missing.
Anyone with ideas?
Challenge 2:
The ALEAUD from SAP Retail (using RBDSTATE) is not referring to the right IDOC from the sending system, seems to me that Retail is using it's own number range.
Anyone with ideas?
best regards
Torstein

Hi,
Even I have the same problem.
I have configured ALEAUD in Integration server. When there is an error ( sa incorect RFC Destination of Receiver), an ALEAUD message type iDoc is sent back to the sender SAP System. But i noticed that the iDoc has only data in the segment E1STATE ( with data status, statxtstamid). But the segments E1AHDHR and E1PRTOB are empty.
The acknowledgement idoc doesnt contain any reference to the message( like the message ID) which has gone for an error. It just contains error text.
Could you please let me know how you solved it
Thanks & Regards,
Vani

Help needed in doing the scenario using BAPI.

Hi...
Please help me out in doing the below sceanrio.
Input is the material number or name.
we have to check whether the material is available or not, and if it is available we have to find out the cost of that material.If the materila is not available we have to get the suppliers to get that material.
This is the scenario.
which type of BAPI we have to use for doing the above scenario.
Please help in doing this sceanrio.
Regards,
Leela

Hi,
Use to this BAPI BAPI_MATERIAL_EXISTENCECHECK and provide the material no as the input. you can check whether that material exists or not.
Also if you want to check the details of a particular material you can use BAPI_MATERIAL_GET_ALL (For costing you can find the details in Valuation data) and also BAPI_MATERIAL_GET_DETAIL
Regards,
Nithiyanandam
Edited by: Nithiyanandam A.U. on Sep 5, 2008 7:53 AM

ALE Configuration using BAPI.

I am adding BAPI in the ALE configuration and as a part of this configuration I have added BAPI in bd64 and I am not understanding how to proceed with other steps.
I want to know the output format for this BAPI from SAP.Answers will be rewarded with good number of points.
Thanks,
Kiran.

Hi Kiran ,
Please check this link
BAPI and ALE
BAPI's with ALE?
Best regards,
raam

Can BAPI Calls in a report trigger an IDOC using BAPI-ALE?

Hi,
I had a requirement to create PO using BAPI. The code is complete. But now I have to use an IDOc instead of BAPI since it is an asynchronous scenario.
Is there any possible way that after CALL BAPI step in the report, an IDOc will be triggered. Is it possible if i set BAPI-ALE?
If yes, do we need to call call_bapi_commit.
Regards,
Sreehari.

hi Shree,
What i understood from u r question is that u need to send teh created PO(created in by bapi ) through IDoc .
Correct me if i m wrong.
you can trigger IDoc from report program easily . I think u have to use bapi _transaction _commit to commit and then trigger IDoc .
And also check the possiblity of change pointer as they r for the same.

Is it possible to use BAPI-ALE to send an idoc using the message control?

Hi Guys
Is it possible to use BAPi-ALE to send an IDOC using a message control?
I have configured the system to send an IDOC when a outbound delivery is saved in the system.
I have done the following.
1). I am using the std BAPI-ALE interface provided by the object type LIKP.
2). I am using the method SAVEREPLICA for which an interface already exists in BDBG transaction.
3). I hace created a distribution model in BD64 and added the BAPI - LIKP and SAVEREPLICA
4). Created a partner profile ( using the generate partner profile option in the BD64 transaction )
QUESTION:
1). How do i associate the custom OUTPUT type created for Delivery ?
2). I tried to associate the custom output type in the Partner profile definition under the message control tab but i am not sure which Process code to be used? Since the partner profile was generated automatically from BD64 it has an entry for SHP_OBDLV_SAVE_REPLICA as a message type in the outbound parameters. and i am unable to find a process code for this Message type in WE41. So what process code should i use in the Message control tab against the custom output type?
3). Do i need to leave the message control tab empty without making any entry? If yes then how would the system come to know that it needs to trigger this partner profile when the custom output type is proposed by the system?
will award points for useful answers
Edited by: Workflow learner on May 29, 2008 8:49 PM

"any way"
Applications such as ScreenRecycler, http://www.screenrecycler.com/ScreenRecycler.html, can do it.

BAPI for cost centers in ALE scenario

Hello All,
We have a requirement to get the list of cost centres from target system when we do F4 on the cost centre field in IT 0001 PA30 transaction or F4 on the cost centre field in cost assignment tab of PPOME transaction. Is there any BAPI that could be set up in the ALE scenario so as to get the list from the target system thus avoiding tranfer of cost centre master between the systems?
Thank you.
Gajanan
Edited by: GajananKerure on Oct 27, 2009 9:00 AM

To complete my question, in fact I need to identify an allocation table which makes the difference between the sender and the receiver. Tables marked "T811" are allocation tables...thanks for your help
Pascal

ALE using BAPI

Can any one specify the steps to be followed for using bapi in ale

Hi,
Please check this link on how BAPI works with ALE.
http://help.sap.com/saphelp_nw04/helpdata/en/4c/4c0eb7725311d396a80004ac96334b/frameset.htm
Hope this will help to start with.
Regards,
Ferry Lianto

ALE IDOC to XML IDOC scenario using XML port

Hi,
I am working on ALE IDOC to XML IDOC scenario using XML port . The requirement is to place a XML IDOC on the application server using ALE IDOC scenario ( output type is created in NACE which is ALE enabled ).
Can anybody help me on the steps.
Regards
Kumar
Moderator message: please search for available information/documentation.
Edited by: Thomas Zloch on Sep 8, 2011 6:01 PM

U can give a try as follows.
In the Partner Profile of Sender R/3 system,
Give the Receiver Party P_Party in the PartnerNo. Give the 'Business Partner' as logical System type.
In XI, Party Definition of P_Party
Give the following Alternative Identifier
Agency -   Sender R/3 Business System
Scheme -   ALE#GP
Value    -    P_Party

BDC Using BAPI

Hi All,
Pls Send me sample code for using Bapi in a Bdc Program to upload Flat file
(non-SAP) Data into SAP R/3 .
Rgds
Rafi .

Hi
You can straight use a BAPI and upload the data into SAP like how you do using a BDC program.
see the doc
BAPI - BAPIs (Business Application Programming Interfaces) are the standard SAP interfaces. They play an important role in the technical integration and in the exchange of business data between SAP components, and between SAP and non-SAP components. BAPIs enable you to integrate these components and are therefore an important part of developing integration scenarios where multiple components are connected to each other, either on a local network or on the Internet.
BAPIs allow integration at the business level, not the technical level. This provides for greater stability of the linkage and independence from the underlying communication technology.
LSMW- No ABAP effort are required for the SAP data migration. However, effort are required to map the data into the structure according to the pre-determined format as specified by the pre-written ABAP upload program of the LSMW.
The Legacy System Migration Workbench (LSMW) is a tool recommended by SAP that you can use to transfer data once only or periodically from legacy systems into an R/3 System.
More and more medium-sized firms are implementing SAP solutions, and many of them have their legacy data in desktop programs. In this case, the data is exported in a format that can be read by PC spreadsheet systems. As a result, the data transfer is mere child's play: Simply enter the field names in the first line of the table, and the LSM Workbench's import routine automatically generates the input file for your conversion program.
The LSM Workbench lets you check the data for migration against the current settings of your customizing. The check is performed after the data migration, but before the update in your database.
So although it was designed for uploading of legacy data it is not restricted to this use.
We use it for mass changes, i.e. uploading new/replacement data and it is great, but there are limits on its functionality, depending on the complexity of the transaction you are trying to replicate.
The SAP transaction code is 'LSMW' for SAP version 4.6x.
Check your procedure using this Links.
BAPI with LSMW
http://esnips.com/doc/ef04c89f-f3a2-473c-beee-6db5bb3dbb0e/LSMW-with-BAPI
For document on using BAPI with LSMW, I suggest you to visit:
http://www.****************/Tutorials/LSMW/BAPIinLSMW/BL1.htm
what is BAPI?
BAPI stands for Business API(Application Program Interface).
A BAPI is remotely enabled function module ie it can be invoked from remote programs like standalone JAVA programs, web interface etc..
You can make your function module remotely enabled in attributes of Function module but
A BAPI are standard SAP function modules provided by SAP for remote access. Also they are part of Businees Objest Repository(BOR).
BAPI are RFC enabled function modules. 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.
The following standardized BAPIs are provided:
Reading instances of SAP business objects
GetList ( ) With the BAPI GetList you can select a range of object key values, for example, company codes and material numbers.
The BAPI GetList() is a class method.
GetDetail() With the BAPI GetDetail() the details of an instance of a business object type are retrieved and returned to the calling program. The instance is identified via its key. The BAPI GetDetail() is an instance method. BAPIs that can create, change or delete instances of a business object type
The following BAPIs of the same object type have to be programmed so that they can be called several times within one transaction. For example, if, after sales order 1 has been created, a second sales order 2 is created in the same transaction, the second BAPI call must not affect the consistency of the sales order 2. After completing the transaction with a COMMIT WORK, both the orders are saved consistently in the database.
Create( ) and CreateFromData! ( )
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
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.sappoint.com/abap/bapiintro.pdf
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#
http://www.sap-img.com/bapi.htm
http://www.sap-img.com/abap/bapi-conventions.htm
http://www.sappoint.com/abap/bapiintro.pdf
u can check the below the material also
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
Reward points if useful
Regards
Anji

Diff... between ALE, IDOC, RFC, BAPI, BADI --- Not clear and clarify

Hi All
    I am learning XI and the difference between " ALE, IDOC, RFC, BAPI, BADI "
    Not clear and when to use what and how in point of XI ?
   Pl..clarify me
Adv..thanks and points
--- Rakesh Behera

Hi
This will expalin you every thing ...pl..go through
The interface concept of the classic R/3 is based on two different strategies: Remote Function Calls (RFC) and data exchange through IDoc message documents. RFC makes direct and synchronous calls of a program in the remote system. If the caller is an external program it will call an RFC-enabled function in R/3 and if the calling program is the R/3 system it will call an RFC-function in another R/3-system or it will call a non-R/3 program through a gateway-proxy (usually rfcexec.exe). BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
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.
The philosophical difference between EDI and ALE can be pinned as follows: If we send data to an external partner, we generally speak of EDI, while ALE is a mechanism to reliable replicate data between trusting systems to store a redundant copy of the IDoc data. The difference is made clear, when we think of a purchase order that is sent as an IDoc. If we send the purchase order to a supplier then the supplier will store the purchase order as a sales order. However, if we send the purchase order via ALE to another R/3 system, then the receiving system will store the purchase order also as a purchase order.
I hope this will help you to understand the difference bet..those
regards
--- prasad

Urgent :Getting error "No ALE scenario active in Profit Center Accounting"

Hi Experts
I am working on a LSWM project ,which uses BAPI BAPI_PROFITCENTER_CREATE for upload of data,but I am facing a strange problem during the IDOC posting the error "No ALE scenario active in Profit Center Accounting" is shown and the status of IDOC goes to 51.
I have done all the ALE setting required for LSMW like File port ,partner type and partner number.
Please help me to solve this error.
Thanks
-Mitesh
Message was edited by:
 Mitesh Parekh

Hi,
Refer This SDN Blog, which gives you steps in detail....
LSMW Step by Step Guide: Legacy System Migration Workbench is an R/3 Based tool for data transfer from legacy to R/3 for one time or periodic transfer.
Basic technique is Import data from Spreadsheet / Sequential file, convert from source format to target format and import into R/3 database. LSMW not part of standard R/3, if we need this product email [email protected]
Advantages of LSMW:
 Most of the functions are within R/3, hence platform independence.
 Quality and data consistency due to standard import techniques.
 Data mapping and conversion rules are reusable across projects.
 A variety of technical possibilities of data conversion.
 Generation of the conversion program on the basis of defined rules
 Interface for data in spreadsheet format.
 Creation of data migration objects on the basis of recorded transactions.
 Charge-free for SAP customers and partners.
Working With LSMW:
Use TCODE LSMW
Objects of LSMW:
Project ID with max of 10 char to Name the data transfer project.
Subproject Used as further structuring attribute.
Object ID with max of 10 Characters, to name the Business object .
Project can have multiple sub projects and subprojects can have multiple objects.
Project documentation displays any documentation maintained for individual pop ups and processing steps
User Guide: Clicking on Enter leads to interactive user guide which displays the Project name, sub project name and object to be created.
Object type and import techniques:
Standard Batch / Direct input.
Batch Input Recording
 o If no standard programs available
 o To reduce number of target fields.
 o Only for fixed screen sequence.
 BAPI
 IDOC
 o Settings and preparations needed for each project
Preparations for IDOC inbound processing:
 Choose settings -> IDOC inbound processing in LSMW
 Set up File port for file transfer, create port using WE21.
 Additionally set up RFC port for submitting data packages directly to function module IDoc_Inbound_Asynchronous, without creating a file during data conversion.
 Setup partner type (SAP recommended US) using WE44.
 Maintain partner number using WE20.
 Activate IDOC inbound processing.
 Verify workflow customizing.
Steps in creating LSMW Project:
 Maintain attributes choose the import method.
 Maintain source structure/s with or without hierarchical relations. (Header, Detail)
 Maintain source fields for the source structures. Possible field types C,N,X, date, amount and packed filed with decimal places.
 Fields can be maintained individually or in table form or copy from other sources using upload from a text file
 Maintain relationship between source and target structures.
 Maintain Field mapping and conversion rules
 For each Target field the following information is displayed:
 o Field description
 o Assigned source fields (if any)
 o Rule type (fixed value, translation etc.)
 o Coding.
 o Some fields are preset by the system & are marked with Default setting.
 Maintain Fixed values, translations, user defined routines Here reusable rules can be processed like assigning fixed values, translation definition etc.
 Specify Files
 o Legacy data location on PC / application server
 o File for read data ( extension .lsm.read)
 o File for converted data (extension .lsm.conv)
 Assign Files to defined source structures
 Read data Can process all the data or part of data by specifying from / to transaction numbers.
 Display read data To verify the input data being read
 Convert Data Data conversion happens here, if data conversion program is not up to date, it gets regenerated automatically.
 Display converted data To verify the converted data
Import Data Based on the object type selected
 Standard Batch input or Recording
 o Generate Batch input session
 o Run Batch input session
 Standard Direct input session
 o Direct input program or direct input transaction is called
BAPI / IDOC Technique:
 IDOC creation
 o Information packages from the converted data are stored on R/3 Database.
 o system assigns a number to every IDOC.
 o The file of converted data is deleted.
 IDOC processing
 o IDOCS created are posted to the corresponding application program.
 o Application program checks data and posts in the application database.
Finally Transport LSMW Projects:
 R/3 Transport system
 o Extras ->Create change request
 o Change request can be exported/imported using CTS
 Export Project
 o Select / Deselect part / entire project & export to another R/3 system
 Import Project
 o Exported mapping / rules can be imported through PC file
 o Existing Project data gets overwritten
 o Prevent overwriting by using
 Import under different name
 Presetting for Inbound IDOC processing not transportable.
One Last thing, Check in BD64 is the Distribution model is Active for Profit Center.
Cheers...
Santosh.D
Mark All the Usefull Answers.

Error Message - No ALE scenario active in Profit Center Accounting

Hi Friends ,
I am uploading Profitcenter master using LSMW Bapi method . I am getting error message " Getting error "No ALE scenario active in Profit Center Accounting" in step - IDOC Processing of LSMW .
I hope i am missing some specific settings for this requirement , any suggestions willl be highly appreciated .
yah i have chekced the same query in sdn , but did not find any solution to that so i am posting this query .
Thanks
Prabhdutta

Resolved by BDC .

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.

Deletion of Scheduling Agreement and Delivery Schedule using BAPI

Hi SAP MM Gurus,
Please assist in inquiry below:
My scenario is that I am trying to delete delivery schedules and scheduling lines using BAPIs. I have no issues when there is no GR made yet for the delivery schedules. The error arises when there are already existing Goods Receipts and Invoices for the schedule line that I wish to delete
When using the BAPIs (either BAPI_SAG_CHANGE or BAPI_SCHEDULE_MAINTAIN), I set the deletion indicator to "L" and set to X all change relevant fields (i.e. DELETION_INDX). However, whenever I execute it, I get the error message 06088. The funny thing is both the Quantities and the delivered quantities that are normally populated are left blank.
For example:
Normal error for 06088:
Quantity 100.0 smaller than quantity delivered 179.0
Error using BAPI with deletion indicator:
Quantity smaller than quantity delivered
Is this a bug of the BAPI? or am I just missing some settings?
Your immediate response is appreciated
Regards,
DeLo

Hi,
Please find the below link check the setting are correct or not
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a02cb00a-bfb4-2c10-98aa-e33e7f64ba28?quicklink=index&overridelayout=true
Reagrds,
Pramod

ALE Scenario using BAPI

Similar Messages

Maybe you are looking for