Material Determination through INBOUND IDOC

Hi Experts,
I have a senario like i need to update the material determination tables when i receive an in bound idoc to create a material. (msg type : MATMAS , Basic type: MATMAS05, Process code: MATM). But i have not seen any segment in the BAsic type to do tht and also there are no user exits for using call transaction after the material creation in the Process code FM. Do u know any BADI or FM can do this. Rewarded with points.
Thanks,
Naren.

Hi,
following are the segments in the Basic Idoc type MATMAS05
E1MARAM                        Master material general data (MARA)
     E1MARA1                        Additional Fields for E1MARAM
     E1MAKTM                        Master material short texts (MAKT)
     E1MARCM                        Master material C segment (MARC)
     E1MARMM                        Master material units of measure (MARM)
     E1MBEWM                        Master material material valuation (MBEW)
     E1MLGNM          Master material material data per warehouse number (MLGN)
     E1MVKEM                        Master material sales data (MVKE)
     E1MLANM                        Master material tax classification (MLAN)
     E1MTXHM                        Master material long text header
     E1CUCFG                        CU: Configuration data
and you search for the CUSTOMER-FUNCTION in the Function module attached to the process code forwriting the User exit part.
Reward points if useful
Regards
Anji

Similar Messages

Populating deliv.add on po line item through inbound idoc

I could not populate delivery address on to po line item in backgroun i.e., through inbound idoc. please help , its a bit urgent.

Hi.
I have one PO 4500000001 for which I have created the inbound delivery 180000001. This inbound delivery has been created through an IDOC. I have another PO 4500000002 having one line item. Now i want to add another line item into the inbound delivery 180000001 for the PO 4500000002 as second line item. To add a second line item to the existing inbound delivery, which IDOC type should I use.
Hope it clarifies the requriement.
Thanks & Regards
Satya

NO MATERIALs in the Sales order created through inbound idoc file

hi,
i have maintained the customer material number as well the SAP Material number in the tcode VD51,but still the inbound
idoc type ORDERS03 is posting the application document(Sales order) without the materials.
for instance,
I have cust.material as CUSTMAT1 in the idoc file.
I have maintained the CUSTMAT1 as cust material and 1001 as material no in VD51.
After posting the inbound idoc file using RSEINB00 prg,the idoc is created and i can see the CUSTMAT1 in the material segment field
The Sales order is created successfully ,but without the materials.
i need the application document has to be posted with materialsm,can any one help me to solve this issue.?
Thanks

Hi ganesh ram
In order to determine the Material Number with you custom material then you needs to have some configurations.
Check with your Functional consultant to add the Access sequence for determining the Material Number with you custom material
In Sale order processes...
Thanks
Ramesh

Create Article Master through inbound IDoc (Normal Flow of Inbound IDOC)

Hi All,
I am new to Inboud IDoc.
I have a file on application server. In program (SE38), I read that file through "open data set"..." close data set.". now the file is in internal table. where should i pass that data (i mean in which structures). and what should i do to create an article in SAP System. I mean what should i write in program ? which Fn. module called ? etc..
My requirement is that using Inbound IDoc ARTMAS05 post the data from application server.
I am aware of all ALE configuration and all WE30, WE31, WE81, WE82.....
could anyone brief the basic steps of inbound IDOC ARTMAS05 and INFREC01.
please help me out.
valuable contribution is appreciated.
Thanks & Regards,

for this you need to write a program .
once you get the data form file to Internal table. then
pass your internal table data to idoc control and idoc dta
like pass all segemnts data then pass all segments data to this FM
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
      EXPORTING
        master_idoc_control            = wa_edidc
      TABLES
        communication_idoc_control     = gt_edidc
        master_idoc_data               = gt_edidd

Re: ME51n through Inbound Idoc

Hi Expert,
Below is the required set up.
"A non-sap system will generate a textfile and the textfile will be push to SAP automatically to trigger automatic creation of PR."
This is my suppose approach but am not sure if this is feasible and how...
1. The text file be output in a ftp server or in a unix directory.
    the text file contain all the info needed to create a purchase
    request.
2. FTP or unix script will push this file to SAP by means of unix or ftp script..
   - any ftp script or unix script for this
3.SAP will acknowledge the textfile
   3.1 trigger event that will generate inbound idoc
       - how to set up the IDOC
   3.2 the inbound idoc will be use to create the PR
       - a customize program running in a background mode which as
         a mode of trigger event
   3.3. the customize program is made of bapi_create_purchase
Does anyone have this requirement before?, any other alternative or better approach to accomplish this? Thanks in advance..
She

Hi,
Please use BAPI_REQUISITION_CREATE to accomplish this.. You'd have to make a remote call and pass the data from the 3rd party system in to the BAPI's structure as a string and it is the nsorted out based on the fields in teh structure..

How to trigger outbound IDOC when data changed in BP through Inbound IDOC.

Hi,
    In our system whenever we create a new Business Partner, these data is send across to SAP R/3 (as BDOC) and to Mainframe system (as outbound IDOC). Whenever we change any Business Partner record the data is send across to SAP R/3 (BDOC) and to Mainframe system (as outbound IDOC).
    This functionality is working fine.
    Currently we are getting a value for one standard field (Customer_Group3) of Business Partner as an inbound IDOC. The value of the inbound IDOC is reflecting in the field (Customer_Group3) in Business Partner Transaction. Once the inbound IDOC is received, the modified value is send across to SAP R/3 as BDOC. But the modified value is not send across to Mainframe system (outbound IDOC). The outbound IDOC is not getting triggered.
Kindly help

Is your mainframe system configured as Site in SMOEAC. If so are you using XIF Adapter.

Additional account assignments could not be determined in inbound idoc

Hi Gurus,
Iam getting the error for inter company billiing idoc .
Direction         2     Inbox
Current status    51 --> Application document not posted
Basic type        INVOIC01
Extension         ZINVOIC2
Message type      INVOIC
Partner No.       I0107IC
Partn.Type        LI
Port              P12INTERCP
Error is : Item: 002 - additional account assignments could not be determined
                Message no. FD171
Please let me know where we can assign the additional account assignment for intercompany billing .
Thanks in advance
RameshG

Check Note 137686 - ALE_INVOIC01: Internal allocatn Customizing in FI
thanks
G. Lakshmipathi

EDI Sales order creation in CRM through inbound IDocs from non SAP system

Hi Friends,
We are having a scenario where we need to create a Sales Order in CRM for a B2B EDI transmission through IDoc. Customer is sending the EDI Transmission of his Sales order , which is passing through PI and then reaching to CRM to create a Sales order.This is the design we need to follow to make it happen,we are initially trying to create an order using WE19 for testing and the details are:
Basic Type - CRMXIF_ORDER_SAVE_M01
Message Type - CRMXIF_ORDER_SAVE_M
Functional Module - APPL_IDOC_INPUTI which is automatically giving a status text as " Function module CRMXIF_ORDER_SAVE has been called successfully", but no sales order is saved in CRM.
We are getting idocs posted successfully with status 53 with the statuses sequence 74, 50 ,64, 62 and 53.Our issue is inspire of the Idoc having status 53 and the FM called successfully we are not seeing the sales order created in CRM.
We are stuck here no sales order is created in CRM.
Are we missing any config. - set up - Prerequisit - Any OSS note need to be applied -- ANy middle ware setting ?
Any help will be greatly appreciated.
Thanks
Vijay

Hi Christophe,
Awesome!!!!!! it worked, You are the best.
I could able to create a sales order in CRM,but below are the valid data I passed in the respective segment fields.Except for first 3 values rest all did not get reflected in teh Sales order.I feel i am missing some qualifiers.
Can you kindly share the IDoc data to be passed in...along with respective segments and fields:
Segment                                                 Field
E101CRMXIF_BUSTRANS     OBJECT_TASK
E101CRMXIF_BUSTRANS     PROCESS_TYPE
E101CRMXIF_BUSTRANS     POSTING_DATE
E101CRMXIF_PARTNER                          PARTNER_NO
E101CRMXIF_PARTNER                RELATION_PARTNER_NO
E101CRMXIF_ORGMAN         SALES_ORG
E101CRMXIF_ORGMAN          DIS_CHANNEL
E101CRMXIF_ORGMAN         DIVISION
E101CRMXIF_SALES             PO_NUMBER_SOLD
E101CRMXIF_SALES            YOUR_REF_SOLD
E101CRMXIF_SALES            PO_NUMBER_SHIP
E101CRMXIF_BUSTRANS_ITEM     ITEM_NUMBER
E101CRMXIF_BUSTRANS_ITEM     ITEM_TYPE
E101CRMXIF_BUSTRANS_ITEM     ORDERED_PRODUCT
E101CRMXIF_PRODUCT_I     PROCESS_QTY_UNIT
E101CRMXIF_PRODUCT_I     PROCESS_QTY_UNIT_ISO
E101CRMXIF_PRODUCT_I     BASE_QTY_UNIT
E101CRMXIF_PRODUCT_I     BASE_QTY_UNIT_ISO
E101CRMXIF_SCHEDLIN_I     ORDER_QTY
Thanks a ton in advance .
Vijay

Creation of Sales order through inbound idoc

Hi,
I'm using two servers 100 and 200.In 100 i'm creating outbound IDOC for PO,In 200 sales order has to be created for that PO.I'm facing some problem in server 200.
Error i'm facing : Partner profile not available.
I done all the basic setting like Logical system,Port and Partner profile creation in both servers.
Kindly advice.
By,
Sathish.

Hi Satish,
Are you sure WEL1 setting is correct?
The message seems to be telling you that it is looking for a vendor with
number 00000000 (zero) which doesn't sound too good to me.
You therefore bill the intercompany customer in sales org 0021 (the
intercompany receivable is in 0021). The intercompany payable is thus in
company code 0043, so that looks right.
Other things to check:
1. Does your IV billing document get generated in sales organisation
0043 with customer 300043 as the bill-to?
2. Check the number of 0's you have in WEL1 Log.addr field. We use
alphanumeric customer numbers for our "internal" customers so there's
not an issue with leading zeroes, but it might be a problem for you. it
seems you've got it right because you've padded with leading zeroes to
get it to 10 long, but you never know.
3. have you created your RD04 condition records in VV31 correctly?
I guess u may find the answer to this link.
http://sap.ittoolbox.com/groups/technical-functional/sap-log-sd/intercompany-billing-edi-partner-profile-not-available-1409203
Thanks
Mohinder Singh Chauhan

How does sap do the material determination for IDOC/EDI?

how SAP do the material determination for inbound PO?
If customer send in their material# or UPC code or buyer material#, what is the order of material determination?
PO1*7CA**UN005650060211VN41112IN515734µ

Hi Samuel,
If the customer sends in their material number this need to be mapped with the value '001' to the field E1EDP19-QUALF and the material number mapped with E1EDP19-IDTNR.
This value is referenced with the CMIR ( Customer material info record) and the vendor's material number is determined which would be used to create the sales order from the inbound PO.
As Such the order of the material determination is depends upon the order it appears in the IDOC.That means the mapping done at the EDI subsystem determines the order of the E1EDP19 segments.
Common practice in EDI inbound P.O scenario,customers send their material number and the vendor material number is determined from the KNMT table.To find the unique material number we need to supply the sales area details as well.
I hope this is answered your question.
Feel free to get back to me if you have any questions.
Thank you.
Regards,
Karun.M

Step-by step procedure for INBOUND IDOC (VENDOR CREATE / CHANGE)

Hi ,
Can any body provide me the step-by-step procedure for Inbound IDOCS.
As i'm new to this i need the the clarification between Inbound & outbound idocs.
How can we differentiate both?
where to define outbound & where to define Inbound?
( If possible Please explain me the procedure for Vendor Create through INBOUND IDOCS )
Thanks in advance..

Hi,
Ale Technology is SAPu2019s technology to support distributed yet integrated processes across several SAP systems.
Outbound Process:
ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
Inbound Process:
The inbound process receives an IDoc and creates a document in the system.
1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
Over view of IDocs:
IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDocu2019s definition and IDoc Data is an instance of the IDoc Type.
IDoc Types:
IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
An IDoc is an instance of an IDoc Type and consists of three types of records.
i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
Message in IDoc Type:
A Message represents a specific type of document transmitted between two partners.
Outbound Process in IDocs:
Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
The Customer Model:
A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
Message control:
Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
Change Pointers:
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
IDoc Structure:
A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
Selection Program:
Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programu2019s design depends on the triggering mechanism used in the process.
Filter Objects;
Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
Port Definition:
A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
RFC Destination:
The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
Partner Profile:
A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocu2019s packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
Service Programs and Configuration Tables:
The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
Process flow for Distributing Transactional Data:
Transactional data is distributed using two techniques: with Message control and without message control.
Process flow for Distributing Master Data:
Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.
Triggering the Outbound Process via Stand-Alone Programs:
Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.
The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.
Triggering the Outbound Process via Change Pointers:
The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.
A standard program, RBDMIDOC, is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.
Processing in the Application Layer:
The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.
Processing in the ALE Interface Layer:
Processing in the ALE Layer consists of the following steps:
u2022 Receiver Determination: The determination of the receiver is done through Customer Distribution Model.
u2022 IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.
u2022 Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.
u2022 Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.
u2022 Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.
u2022 Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.
u2022 Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).
u2022 Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc u2013 Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch u2013 ALE Service).
u2022 IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).
Processing in the Communication Layer:
To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.
Inbound Process in IDocs:
An inbound process used IDoc structure, posting programs, filter objects, conversion rules, a partner profile, service programs, and configuration tables to post an application document from an IDoc.
Posting Program:
Posting programs, which are implemented as function modules, read data from an IDoc and create an application document from it. A posting program exists for each message. Each posting program is assigned a process code. A process code can point to a function module or a work flow. In the standard program process codes always point to a function module.
Ex. The posting program for message type MATMAS is IDOC_INPUT_MATMAS which has a process code MATM.
Workflow:
A workflow represents a sequence of customized steps to be carried out for a process. The workflow management system is used to model the sequence, identify information required to carry out the steps and identify the person responsible for the dialog steps.
Partner Profile;
A partner profile specifies the components used in an inbound process (partner number, message type, and process code), the mode in which IDocs are processed (batch versus immediate), and the person to be notified in case of errors.
Process flow for the Inbound process via a Function Module:
In this process, IDocs are received from another system and passed to the posting function module directly.
1. Processing in the communication Layer:
The IDOC_INBOUND_ASYCHRONOUS program, triggered as a result of an RFC from the sending system, acts as the entry point for all inbound ALE processes. The IDoc to be processed is passed as an input parameter. Control is transferred to the ALE/EDI layer.
2. Processing in the ALE/EDI Interface Layer:
u2022 Basic integrity check: A basic integrity check is performed on the control record.
u2022 Segment Filtering and conversion: Filtering out unwanted segments and carry out any required conversion of field values.
u2022 Creation of Application IDoc: The application IDoc is created and stored in the database and a syntax check is performed. If there are errors it gets status code of 60 (Error during Syntax check of IDoc u2013 Inbound). At this point a tangible IDoc, which can be monitored via one of the monitoring transactions, is created and the IDoc gets status code 50 (IDoc Added).
u2022 IDoc Marked ready for Dispatch: IDoc gets the status code 64 (IDoc ready to be passed to application).
u2022 IDoc is passed to the posting program: The partner profile table is read. If the value of the Processing field is set to Process Immediately, the IDoc is passed to the posting program immediately using the program RBDAPP01.
3. Processing in the Posting Module:
The process code in the partner profile points to a posting module for the specific message in the IDoc. The posting program implemented as a function module either calls a standard SAP transaction by using the Call Transaction command for posting the document or invokes a direct input function module.
The results of execution are passed back via the function moduleu2019s output parameters. If the posting is successful IDoc gets the status code 53 (Application Document Posted) or it gets status code 51 (Error: Application Document Not Posted).

Differnt material in order and idoc

Hi,
I have a standard order that is created through inbound idoc.
The data segment in the idoc shows a differnt material while that present in the created order line item is different.
What could be the possible reason and where can I check the same.

Hi
Use T code WE60 to search for the segment documentation of IDoc type
IDoc needs three different kinds of segment types:
E1EDK01 is the main segment of an ORDERS01 IDoc.Used for calling program to pass the SAP IDoc syntax check.
E1EDP01 is the segment for a single order position. The field MENGE contains the quantity. Of course, this segment can occur more the once.
E1EDP19 represents an object definition. In this case the object is a material number. The field QUALF is therefore set to 002 and the material number is written into the IDTNR field. E1EDP19 segments are always children of E1EDP01
Rohit

Inbound IDOC status is strucked at 64

Hi,
My rerequirement is as follws.
Inbound IDOC process:
Through inbound IDOC i have to create the new sales orders and need to change some information to existing sales orders means 2 cases.
1) Create new sales order
2) Change existing order.
Iu2019ve generated two example IDOCs from order interface
one for an u2018order addu2019 and one for an u2018order changeu2019.
The times each IDOC reached each status are shown below:
IDOC 1677672 u2013 Order ADD
Status: 50 Started         Time:    09:54
            64 IDOC ready               09:54
            62 Direct Call                 10:39
            53 Order Created           10:39
IDOC 1677684 u2013 Order CHANGE
Status: 50 Started         Time:    12:50
            64 IDOC ready               12:50
            62 Direct Call                 12:50
            53 Changes on Y-table   12:50
Can anybody explain why the first IDOC had to wait for the scheduled
u2018IDOC PROCESSINGu2019 job to run, before it moved from status 64 to 62. But
the second IDOC appears to have been processed automatically without
waiting for the next run of the scheduled job?
Obviously, the u2018automaticu2019 processing of the change IDOC is the way we
would prefer it to work all the time).
Can any body explain in first case why it's taking time and in second case it's processed immidiately.
Regards,
Janardhan

Hi,
I believe you are using two different message types for this purpose. One to create order and one to change order. Did you check the partner profiles for these? May be partner profile(WE20) for creating order is set as "Collect Idocs" whereas the partner profile for the message type to change order is se as "Trigger immediately".
Hope it helps.
Regds,
Rudra

EDI: Extending VB12 - Material determination.

Hi everybody.
Sorry if I'm posting a wrong place - but has been away from SCN for a while....
I'm working with EDI and we wants to extend Material determination for inbound Orders so that Partner Profile is part of the selecttion.
so instead non "only" SOrg/DistCh/Mat is the key combination but also eg Partner Type KU ( from T-code WE20)
I have searched but not found anything usefull.
Any hint will be rewarded :-)
Best regards
Lars Henrik Andersen

Solved..

Any IDoc/BAPI for Loading Material Determination Condition records - VB11??

Hi All,
I need to load the material determination condition records which can be done through the transaction VB11. I dont want to do load the records through BDC.
So, I am looking for any IDoc or BAPI which can do this job.
Any help in this regard is highly appreciated.
Points will be awarded for all useful replies.
Thanks in advance,
Surendra K

hi surendra,
i have a exact same task to load material determination to SCM
"load the material determination condition records which can be done through the transaction VB11. I dont want to do load the records through BDC, i am looking for any IDoc or BAPI which can do this job"
thank you
sridhar K

Material Determination through INBOUND IDOC

Similar Messages

Maybe you are looking for