FM to get partner profile details for ALE-IDOCs?

hi
is there any function module to get partner profile details in current system?
extremly sorry my mistake......
for ALE-IDOCs
Message was edited by:
ashwinee mali

BAPI_BUSINESS_PARTNER_MODIFY CBP: BAPI for Modifying (Creating/Changing) Business Partner
BAPI_BUSINESS_PARTN_GET_DETAIL CBP: Business Partner Detailed Information
regards,
srinivas
*reward for useful answers*

Similar Messages

Partner profile details for WBI

Hi all
    this is my requirement.we need to send a file from WBI to SAP as IDOC.i want to know about sender details(i.e) sender port ,sender address,partner number.just suggest me about these things
    Thanks in advance

Hi ,
          Please refer the folowing links
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
Configurations in R/3 side
1. SM 59 (RFC destinations)
Create a RFC destination on the XI server. The connection type should be R/3 connection. The target host needs to be the XI server.
2. WE 21 (Ports in IDOC processing)
Create a transactional port. Provide the RFC destination created in this.
3. BD 54
Create a logical system.
4. WE 20 (Partner Profiles)
a. Create a new partner profile under partner type LS.
b. Assign the message type in outbound parameters.
c. Open the message type (Dbl click) and configure the receiver port to the port created.
Configurations in XI server.
1. SM59 (RFC destination)
Configure the RFC destination specific to the R/3 system.
2. IDX1 (Port maintenance in IDOC Adapter)
Create a port and provide the RFC destination.
TESTING:
WE19 For pushing the idoc in xi through trfc port.
To be able to trigger your IDOC from the SAP ISU system, you will have to set the partner profile in we20. Select your Business System (mostly under Logical system) and then create Outbound entries for whichever IDOC you want to trigger.
You define your basic type also in your partner profile settings, Please go thru the following links to get a better idea about partner profile:
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b833243d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7cd343d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/32/692037b1f10709e10000009b38f839/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5e/b8f8bf356dc84096e4fedc2cd71426/frameset.htm
Also, I would suggest that you go through this blog by michal if any issue arises,
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
Assign points if you found helpful
Regards.,
V.Rangarajan

Issue in Partner Profile config for Outbound IDOC

Hi Experts,
I have requirement like, When ever there will be any change in a Sales Order an Outbound IDOC will get triggered though a output type. This IDOC will save a file in the Application Server.
The Message Type i am using is ORDERS and the Basic Type is ORDERS05.
I have created a Partner Profile also a Receiver Port of type FILE.
I have Assigned Message type in Outbound Parameters.
I have assigned Receiver Port and Basic type under "Outbound Option".
I have Assigned Applications as 'V', Message type as 'Output Type' and Process Code under "Message Control".
When i am changing any Sales Order no IDOC is getting Triggered. I checked the Sales Order>Extras> Output> Header> Edit, the Output type is in Status RED with Message " No Partner Profiles (Message Control) Maintained".
Please guide me if i have missed any configs.
Help me solving this issue.
Thanks in Advance!
Priyabrata

Hi Priyabrata,
please try changing in your partner profile the application from V to V1. Another problem that's often causing the partner profile not to be found are the partner functions that are added automatically by SAP, but sometimes forgotten in the partner profile.
I don't have a SAP system at the moment, but as far as I remember the long text of the message indicates the partner profile parameters that SAP uses for the lookup.
If all of this doesn't help, I'd quickly debug this and see why SAP's not picking up the correct partner profile.
Cheers, harald

Function module to get the payment details for PO

Hi,
Is there any standard function modlue to get the payment details for specific purchase order or is there any table where we can get the payment details till date.
My requirement is purchase order wise how much already paid to vendor and what is the balance amount to be paid vendor.
thanks in advance....
Regards,
Sree

Hello
BAPI_PO_GETDETAIL will help you.
Look at structures PO_ITEM_HISTORY and PO_ITEM_HISTORY_TOTALS
Also you may use table EKBE

Steps for ale idoc creation?

Hi,
I want the complete process of ale idoc generation.
my maild id is [email protected]
Thank You.
From:
Mohammed Moid Ahmed

Hi
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
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
Reward points if useful
Regards
Anji

Technical requirement's for ALE/Idoc

Hi all,
Am new for ALE/IDOC
we have requirement for ALE inbound and outbound scenarios ,
what are the mandatory requirements(port,partner profile, message type ..etc) from technical point of view for Technical consultants,
Regards
Suresh.D

Here is the step-by-step configuration approach in ALE.
- Create logical system (txn BD54)
- Assign client to Logical system (txn SCC4)
- Create RFC destination (txn SM59)
- Generate ports (txn WE21)
- Create partner profiles (txn WE20)
- Create distribution model (txn BD64)
Now you can use the required transactions like BD10 (to send materials), BD12 (to send customers), BD14 (to send vendors)....which would create the IDocs. You can view the generated IDocs via txn WE02 as you note down the system time when the IDocs are generated. You can use txn BD87 too to trace the IDocs at the sender...
If idoc is in status 51 or 52 process by program RBDMANI2 or in transaction BD87, If idoc is in 64 status process the idoc by program RBDAPP01.

Material for ale,idoc programming

Hi folks,
i need urgently the material for IDOC programming.i am mentioning the process below.
1)i have created one program. i need to send some fields to a folder through IDOCS.
when i will press a push button on my program, this idoc program should execute so that some of the fields will transfer through IDOCS.
Thanks

hi,
Intermediate Documents (IDOCs)
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.
The two available process for IDOCs are 1) Outbound Process 2) Inbound Process.
There are basically two types of IDOCs.:
1. Basic IDOC type defines the structure and format of the business document that is to be
     exchanged between two systems.
2. Extension Idoc: Extending the functionality by adding more segments to existing Basic IDOCs.
-To Create Idoc we need to follow these steps:
1. Create Segment      ( WE31)
2. Create Idoc Type      ( WE30)
3. Create Message Type ( WE81)
4. Assign Idoc Type to Message Type ( WE82)
1. Creating a Segment:
nGo to transaction code WE31
nEnter the name for your segment type and click on the Create icon
nType the short text
nEnter the variable names and data elements
nSave it and go back
nGo to Edit -> Set Release
nFollow steps to create more number of segments
2. Create Idoc Type      (WE30)
nGo to transaction code WE30
nEnter the Object Name, select Basic type and click Create icon
nSelect the create new option and enter a description for your basic IDOC type and press enter
nSelect the IDOC Name and click Create icon
nThe system prompts us to enter a segment type and its attributes
nChoose the appropriate values and press Enter
nThe system transfers the name of the segment type to the IDOC editor.
nFollow these steps to add more number of segments to Parent or as Parent-child relation
nnSave it and go back
nnGo to Edit -> Set release
3. Create Message Type (WE81)
nGo to transaction code WE81
nChange the details from Display mode to Change modenAfter selection, the system will give this message The table is cross-client (see Help for further info). Press EnternClick New Entries to create new Message Type
nFill details
nSave it and go back
4. Assign Idoc Type to Message Type (WE82)
nGo to transaction code WE82
nChange the details from Display mode to Change moden After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
nClick New Entries to create new Message Type.
nFill details
nSave it and go back
There are three types of records :
nControl Record                          nData Record                                     nStatus Record
Control Record - contains the key information like destination, IDoc type, message type, port and sender information. Control records are of EDIDC type of structure.
Data Records - This contains two parts.
nAdministrative Section and Data Section
nAdministrative Section consists of Idoc number, Segment Name, Segment number, Version, Segment Hierarchy etc.
nData Section contains the data of respective segment
nData records are of EDIDD type of structure
nStatus Record - whenever a process is taken place, system will generate status records.
nWe can identify the process with the number of status record.
n01 - 49 for Outbound Process
n50 - 75 for Inbound Process
nwhen IDoc is processed the messages are:
n01 - IDoc is created
n30 - IDoc is ready for dispatch
n03 - IDoc is processed
check all the below links u will find lot of info
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
For ALE -- IDoc's
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
ALE/ IDOC/EDI
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.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
ALE/ IDOC/ XML
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
http://www.angeli.biz/www5/books/IDocBook/IDocBook.pdf
IDOC Convertion
/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
~~Guduri

Upgradation procedure for ALE/IDOCS

Can anyone let me know what is the upgradation procedure for ALE/IDOCS and what are the steps needs to be checked out during technical remediation part of version upgrade(lower version to ECC6.0)?

IDocs are backwards compatible, so I don't think you need any special procedures for them, just a regular test, to make sure everything stull works fine. If you've had extended any standard IDocs, that part will need to be reviewed, as any other custom development.
However, there might be a newer version of the IDoc type available in ECC 6.0, which you didn't have in the previous release. You might want to see if there would be any benefits in switching to the newer version.
I'm sure you'll find all the information on the Upgrade page on SAP's [web site|http://service.sap.com/upgrade]. Also there is an SAP Press book on the subject.

ALE partner profile setup for diff. IDOC extension

Hi,
We have three extensions of IDOC type HRMD_A06 and message type HRMD_A. In one of the extensions segment IT0002 is extended.
In the partner profile extension is not specified. Due to this when the IDOC is generated Custom segment is not getting picked up.
I pu the extension in the partner profile then it woks fine.
But I do not want disturb the existing profile setup. Is there any option in WE20 where we can define two profiles with one message type, basic type and different extensions.
Also if we define the custom message type then distribution model and the partner profile needs to be generated for the new custom message type.
Appriciate quick response.
Regards,
Sonali

Hi,
just check the FM 'BAPI_BUPA_CENTRAL_GETDETAIL'.
Or just search for oher FMs with BAPI_BUPA*.
Hope this helps...
vasanth

How is partner profile for ALE/IDOC transported?

Hi experts,
How is a request created for transporting configurations in ALE/idoc.
Valuable answers will be generously rewarded.
regards,
Shrita.

Hi,
some configurations are client dependent and some are client independent.
so client dependent configurations are transported to different clients using SCC1 transaction.
and client independent configurations they refelect automatically.
Regards
vijay

Partner profile value for XI system

I got a outbound message with partner profile value as
<SAP:SNDPOR>XIDEV</SAP:SNDPOR>
<SAP:SNDPRN>XiALE01</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
Where do I go and change the SNDPRN value in SLD? or is it SLD I change it. SAP R3 is looking for sender partner profile in caps. How to change this value in XI
thanks

Hi,
Please update few things.
1. Since it is an outbound from XI into another R/3 machine, I would first suggest you to check IDOC posted in R/3 which has an error message tagged to it. This is applicable only when Message went from XI into R/3 and we see an error in the SXMB_MONI as RFC destination not found etc.,.
In such a case, IDOC error message with 53/51 etc, will post an error message like "SENDER NOT IDENTIFIED". This SENDER and RECEIVERs can be seen in the CONTROL RECORD of the IDOC.
From R/3, use transaction WE02/WE05 and locate your IDOC (normally in the OUTBOUND folder on left, look at last few messages which have RED TRAFFIC SIGNAL and match the partners).
To resolve this, create the RFC PORT first. XIDEV using WE21 referring to your XI client. The prerequisite for this is to have a RFC destination already created to port XI and a logical system (BD54 transaction).
Create a Logical System (Business Partner) of type LS using WE20 and (Logical system you have created or identified in BD54) should be configured as you want.
This should resolve your issue.
2. If the issue is with XI and message is not seen in R/3, make sure you have assigned proper logical system in the SLD for your technical landscape. If this is pointing to a different logical system, then probaboy you may want to change to suitable logical system.
Suggest you to look for the definitions using SM59 and IDX1 in R/3.
Hope this answers, please let us know your findings.
Thanks,
Srini.

Partner Profile configuration for EDI 810

Hi,
I am configuring partner profile for EDI 810 (Invoice). In the message control tab, what values should be entered for
1. Application
2. Message Type and
3. Process Code
Thank you.

Hi,
- Check Transaction NACE to see what applicatios you can use for different objects.
- Check transaction WE42 for all outbound process codes
- Check transaction WE41 for all inbound process codes.
- Check transaction WE64 for inboud / outbound message types and related process codes.
EDI 850:
Application - EF
Process code - ME10
Message type - NEU ( or your custom message type setup for EDI )
IDOC - ORDERS01 to ORDER05
EDI 810:
Application - V3
Process code - SD09
Message type - RD00 ( or your custom message type setup for EDI )
IDOC - INVOIC01 , INVOIC02.
EDI 820:
i think this is for inbound idoc of Payment Order/Remittance Advice. When yuo setup inbound partner profile, you do not need to know application
Process code - LOBX
Message type - LOCKBX
IDOC - PEXR2002
Let me know if you need any other information.
Regards,
RS

Function module to get the BOM details for a material-plant combination

hi
Is there any function module to get the BOM details such as
 BOM Usage -STLAN
 Alternative BOM -STLAL
 Items -POSNR
 Required Quantity-EMENG
 Resulting Quantity-MENGE
 Unit of measure -BMEIN
 Base unit of measure-MEINS
for a given material-plant combination
if so please suggest me some FMs.................
Awaiting for ur reply..............

try the below fm it may be useful for you
DATA : BEGIN OF I_BOM OCCURS 0.
 INCLUDE STRUCTURE STPOX.
DATA : END OF I_BOM.
CALL FUNCTION 'CS_BOM_EXPL_MAT_V2'
 EXPORTING
 CAPID = 'PP01'
 DATUV = SY-DATUM
 MEHRS = 'X'
 MTNRV = P_MATNR
 WERKS = P_WERKS
 TABLES
 STB = I_BOM
 EXCEPTIONS
 ALT_NOT_FOUND = 1
 CALL_INVALID = 2
 MATERIAL_NOT_FOUND = 3
 MISSING_AUTHORIZATION = 4
 NO_BOM_FOUND = 5
 NO_PLANT_DATA = 6
 NO_SUITABLE_BOM_FOUND = 7
 CONVERSION_ERROR = 8
 OTHERS = 9.
IF SY-SUBRC <> 0.
 MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
just befor use it check your application area.for my case it is PP01. you can find it in CS12 when you are exploding the bom the value you are giving in BOM application that is the value for CAPID.
Just go to se37 and checkout the fm it has lot of options here I am using the minimum things.
regards
shiba dutta

Partner Profile settings for IDOCs

Hi,
when i posted the IDOC, it left the status 51.
i think which means "Application not posted".
do i need to change the partner profile!
if yes please let me know how to change that.
its very urgent please.
thanks in advance.
Regards,
ravi.

As mentioned in the earlier reply you need to check idoc listing WE02.
You may also want to look into the partner profile- WE20 and see if what you are trying to pass thru has been set up correctly. Make sure the correct port is defined along with the partner details.
If you need to edit the IDoc , you can do it from WE02 by clicking on the segment and then going into the Change mode. The other option of re- processing Idocs is using the testing tool- WE19 or the re-process Idocs BD87 transactions.

BAPI Function Get partner profiles of message type

Hi Gurus!
Does anyone know any function module or bapi to retrieve the partner profiles / logical system of a message type?
For example, if message type ZMATMAS is in two different logical systems, I would need to retrieve both those logical system.
Thanks!
Adi

I have played around a bit, and found out that the table where this info is stored is EDP13 - therefore this solves my problem...
Nevertheless, if anyone knows a good function module/ BAPI please let me know!
Thanks Gurus!

FM to get partner profile details for ALE-IDOCs?

Similar Messages

Maybe you are looking for