Material creation using IDOC

Hi All
We are trying to create a Material with just a Basic View using FM : IDOC_INPUT_MATMAS01, but we are unable to do the same since it returns errors about fields to be filled for other Material master views
like Plant , Sales Organisation etc
Has any one succesfully created a material using this FM
Please let us know ,
Thanks in advance

Hi Sanjay,
These are the related programs related to your question.
RBDARTS2 Posting of retail materials to your own system via IDocs
RBDARTST Reimport IDoc Directly to Inbound Processing of Retail Material Master
RBDFEART Get retail material
RBDFEMAT Get Material
RBDMATS2 Post Materials via IDocs to Your Own System
RBDMATST Reimport IDoc Directly to Inbound Processing for the Material Master
RBDSEART Send retail material
RBDSEART_DXWB Send Material (Data Transfer Workbench)
RBDSEBOM Material BOM Distribution
RBDSECNP Distribution of Configuration Profiles for Materials
RBDSEMAT Send Material
RBDSEPAM Plant allocations to material BOMs distribution
RBDSESTT Distribution of material variants
RBDSEWG1 Direct transfer of base material groups
RBDSEWGR Direct Transfer of Material Group Hierarchies
You can use this standard program to generate IDoc(s) for material master.
RBDSEMAT
RCCLMAT
You can check the EDIDC (data control) of an IDoc (WE02) to ensure correct and match with your partner profile (WE20).
Reward points if helpful.
Regards,
Harini.S

Similar Messages

Material Creation Using BDCs.

Hi all,
I have developed a program for Material Creation using BDC.
Material is Being created and that is working well and good.Here i have a Requirement to update the Newly creted material in Ztable.So when i use call transaction mathod,i have written code for updation under the line CALL TRANSACTION.where in iam getting newly creatde material from MARA table,and so it is working perfectly fine..
But our requirement should be sessions method,so when i use sessions method and exeute the program..we face the problem of updation.
the piece of code for updation is updating previously created material.
Literally speaking only the sessions are created ,when the program is executed,material is not created when program is run.Material is only created when the sessions are processed using SM35,
So how should i do here,where should be the updation code written and where will we get the newly created material in sessions method..
Pls Help me in solving this problem

hai priyanaka it might be due to configuration problem
bcos manulay also ur gettign this , so just consult ur MM consultant for soem setting
regards
afzal

Error when ECO and BOM creation using IDoc

Hi experts,
now i am doing an interface about ECO/BOM creation and changing using IDoc.The idoc type is ECMMAS02 ans BOMMAT04.
since i know a little about ECO/BOM, can anyone provide some good materials for me?
and i don't know which fields are mandatory in idoc segment, so i go to tansaction BD30 to run a BOM changing. i input a change number but the idoc log shows that change number does not exist. what is the change number using? where i can implement the changes, e.g, change the quantity? should the change number be used when creation and changing? how can i get this change number?
thanks a lot in advance!

Hi experts,
now i am doing an interface about ECO/BOM creation and changing using IDoc.The idoc type is ECMMAS02 ans BOMMAT04.
since i know a little about ECO/BOM, can anyone provide some good materials for me?
and i don't know which fields are mandatory in idoc segment, so i go to tansaction BD30 to run a BOM changing. i input a change number but the idoc log shows that change number does not exist. what is the change number using? where i can implement the changes, e.g, change the quantity? should the change number be used when creation and changing? how can i get this change number?
thanks a lot in advance!

Customer master creation using IDOC

Hi friends,
           I am trying to create customer master into SAP using Idoc. Here pblm is some partner functions already defaulted i want to create some new entries in partner functions when i try to do it online its working fine when i try with idoc the defaulted partner functions are appears double times can any one has any idea whts happening.
E1KNVVM
    E1KNVPM (Master customer master partner roles)
        MSGFN : Function
        PARVW : Partner function
        KUNN2 : Customer number of business partner
        DEFPA : Default partner
        KNREF : Customer description of partner
        PARZA : Partner counter
the pblm is with these segment.
Thanks,
Naren.

Hi naren,
The segment E1KNVPM is standard one.Nothing can be done over it . U shold create new segments in we31 and add as
extension to the basic type and try..
Regards,
Nagaraj

LSMW - Sales Order creation using IDoc

Hello,
I'm receiving a file containing different category of products and need to create a sales order (using IDoc or BAPI) per category. The input file contains UPC code, I use a SELECT statement to check the category and append the UPC code to the specific internal table .(one internal table per category). The issue I have is to do loop in all internal table and then to create a sales order. I have some difficulties to update item segment. Only one UPC is populated to the required segment. Please let me know if this could be done using LSMW.
Thanks ! Thanks ! Thanks ! Thanks !
Mehdi

You can use program RVINVB10 ( Direct Input ) to create Sales Order , Before you run this program you will have to create a file with data in specific format.
Read the documenatation of the program.
LSMw can help in formatting the data but beetr write your own progarm to format data and then run above program as LSMW has limitations and I am not sure what type of file you are getting. In you custom program you will have more control.
Cheers.

Stock Transfport Order Creation using IDOC

Hello Everybody,
I am trying to create a Stock Transport Order using IDOC's. All configuration for the STO has been done and I have no problems creating these orders using ME21N.
Now I need to create STO using IDOC. I am using Message Type ORDERS and Basic Type ORDERS05, but I am not sure what Process Code to use in the Partner Profile configuration in order to pick up proper processing module....
Any help would be appreciated,
Than you in advance
Felix

I ended up writing my own processing FM for this and used BAPI_PO_CREATE1 to post the PO

Material Change using idoc

Hi Experts,
Need your advise,
Actually my scenario is, that i am creating the Material using inbound idoc with Basic Type: MATMAS05 and Message Type: MATMAS,
now i need to change the same material, how can i achieve that??
Say, I have created a Material with MATNR: ABC using inbound MATMAS idoc, now how can i change it??
Aayush

It always depends on what you need to change.
In general you just need a new IDOC with the new values for the same material number.
It will automatically overwrite the old values, except you want to change values that are no longer allowed to be changed.

How to maintain inspection type at the time of material creation using LSMW

Hi All,
I have a differnet Issue.
I am using a std. LSMW to create the materials.
But now using same LSMW i have to maintain Inspection types(ART-RMQAM) for the materials to be created.
How this can be done.
This filed is not found in any structures like BGR....to BMMH8
Can I create such a structure ??
Amol

Some need the hard answer: it is not possible in one go.
It is an embedded functionality in material master like classification, but it is not stored in a material master table.

PO Creation Using IDOC ORDERS05 - Inbound Issue

Hi Experts,
I am new to the ALE/IDOCs. I am trying to create a PO in one client and trasnferring it to another client using the IDOC extension. I am using Message type ORDERS and Basic type ORDERS05 (Extended). I have craeted Partner Profile for both Inbound and outbound in their respective clients.From Outbond the Purchase order is sent successfully to the Port. On the inbound the PO is failing due to incorrect function mudule chosen for processing through process code. I have tried process codes like ORDE,ORDS,DELO and ME11.
Please Let me know the corrects process code in the inbound, to process IDOC as PO.
If i need to go for all together a different mesasge type. Please give me all the relevant details like BASIC type, Process code in Inbound and outbound . And i want the BASIC type to be extensible.
Thanks,
Murali

Hi,
In the inbound side create a new entry in WE57 tcode.. with the functio mdoule as "IDOC_INPUT_ORDERS", basic type "ORDERS05", extn< specify the extn u created at outbound side>, message type "ORDERS". Now see if it is working.
Regards,
Nagaraj

Material Creation using Workflow

This is my scenario .
Initially when a new Material created it will have only the Basic 1 & 2 views alone .
At the same time a workflow have to be triggered such that it have to send to a workitem to person who should define the MRP views only not other views of the material after it is finished another workitem to another person to define the account assignment views only not other views .Kindly help to proceed.
- David Boon.

Hi Martina,
If you have done that then you are almost on the verge of completion!
Follow this binding procedure between the task container and the method container and get the results.
In the BO method, add an output parameter that would store the plant detail.
Now create a data element in the method code of the same type as plant detail type.
Then use swc_set_element to store the value of the plant detail in the output parameter.
In the workflow task, create an output parameter of the same type as the BO method output parameter.
In the binding between the task container and the method container fetch the value of plant details from method container to task container element.
Now pass this parameter to the workflow container and use in the send mail step in the mail text.
Make sure to save and generate the BO after doing all the changes.
Regards,
Saumya

Material Master Creation Using BAPI

Hi,
I m using BAPI_MATERIAL_SAVEDATA for Material creation using BAPI.
Now the problem is , i have created a Screen exit long back in Purchasing view.. the corresponding Z field is created in table MARC..
How can i pass value to this Z field using BAPI.
i tried with BAPI_MARC.. my Z field is not coming in that structure.
Can anyone guide me how can this be achieved.
Thanks in Advance
Aravindh Mani

Hi,
The Function Module BAPI_MATERIAL_SAVEDATA has the options to pass the Z fields. There exits a structure parameters
EXTENSIONIN
EXTENSIONINX
in BPAI. In EXTENSIONIN pass the data and value part you can pass in EXTENSIONINX. So this will update the Z fileds in material
master .

Creating a BP in CRM through LSMW using IDOC

I am trying to create a buss partner in crm through LSMW using IDOC:
Message Type: CRMXIF_PARTNER_SAVE_M
Basic Type: CRMXIF_PARTNER_SAVE_M02
I get an error: "No update is defined for BP role 000000".
I am also filling
IDENTIFICATIONCATEGORY: CRM001
IDENTIFICATIONNUMBER: 12345678
However i get this error only if the external ID does not exist in table BUT0ID.
otherwise if the external ID is present in table BUT0ID and the object task is "U"pdate, the BP is saved.
Has anybody worked on BP creation using IDOCs? If yes please guide me.

Hi,
This Check Box is required for Archiving Business Partners from the System. You can have a full idea about the same from the link below [Archiving Business Partners|http://help.sap.com/saphelp_crm60/helpdata/en/52/cff837a9aae651e10000009b38f8cf/frameset.htm]
Also have a look at the following [Introduction to Data Archiving (CA-ARC)|http://help.sap.com/saphelp_crm60/helpdata/en/8d/3e4c11462a11d189000000e8323d3a/frameset.htm]
Hope this helps.
Thanks,
Samantak.

Creation of PO using IDOC's

Hi,
I am trying to create a PO, using IDocs, in the SAP system. The IDoc will come from a non-SAP system - hence, this is an inbound interface.
Can someone please tell me which Message Type / IDoc Type I should use?
As well, I need to create Characteristics for the Purchase Order. So, I need an IDoc that allows me to create these.
Two options (using existing IDocs):
1. ORDERS/ORDERS05
I have read some of the help documentation and some of the messages posted on this forum and found that the ORDERS/ORDERS05 is used for outbound PO IDocs, and inbound SO IDocs.
Can someone please confirm or correct me? So, this option is OUT.
2. PORDCR/PORDCR05
Apparently, PORDCR/PORDCR05 can be used for inbound PO. However, it does not contain segments for Characteristics. Hence, I will need to extend the IDoc. However, there aren't any useful user-exits to handle the creation of Characteristic values!
Any ideas or suggestions will be greatly rewarded .
Thanks
Bobby

on your points
#1is correct.
#2 yes, if you need any other functionality you need to extend the IDOC. alternately look at BAPI_PO_CREATE* BAPIs to see if they fulfil your requirements

Creation of Delivery Using IDOC without reference to order

Pls suggest is there is any way to create delivery using idoc without reference to order. This is very urgent.

Hi
Design the inbound idoc in such a way that it carries all the essential data needed to create a delivery document namely the material number, no of units to be deilvery, delivering plant, storage location, shipping point, warehouse number(if applicable) etc.
Pass all these details to the function module RV_DELIVERY_CREATE while creating delivery in VL01N and pass the document type as LO which is delivery document without reference to order.
But it is advised to have atleast a pseudo order with which we have to create the delivery document.
Pls reward points.

Sales Order Creation using LSMW IDOC method.. ( Custome Interface)

Hi ABAP'rs,
                 Please provide me LSMW steps for creating Sales Order using IDOC method.
                        Thanks and Regards,
                                              Param.

LSMW-IDOC in General
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.
Reward if useful.
regards
santhosh reddy

Material creation using IDOC

Similar Messages

Maybe you are looking for