Transfer Material Master (MATMAS) Idoc into Retail Article Master (ARTMAS)

I need to transfer data from an SAP 4.7 ERP system that is set up for material masters to a different SAP 6.0 system that is set up as Retail.
The question is which system should be doing the conversion to the ARTMAS
Option 1: The outbound IDOC would be a MATMAS05 and it would be recieved and converted on the Retail side to an ARTMAS doc to create the articles.
If this is the case do you know how this needs to be set up on the retail side, for this conversion to occur.
Option 2: Translate the material master and send out an ARTMAS IDOC from the ERP system In this case I think that we will need a lot of custom code, and the SAP sending box will need to perform conversions that are known only on the retail side.
I am not really asking for the exact configuration set up
What I am looking for is how if other companies are doing this which option is considered the standard/best practice

Question was never answered we will need to determine how best to do this.

Similar Messages

How can i change my old master card account into my new master card account in app store?

HOw can i change my old master card account into my new master card account?

Howdy Aldringwapo,
Thanks for using the Apple Support Communities.
To change the payment information associated with your Apple ID, follow the directions in the article below.
Change or remove your payment information from your iTunes Store account (Apple ID) - Apple Support
Have a good one,
Alex H.

SAP Retail : Article Master Data Transfer using LSMW/ARTMAS05: EAN Error

Hi Bjorn Panter,
I want to thank you for providing very informative articles on the Master Data of ERP Retail.
We are currently loading articles to SAP from legacy and use your articles on ERP Retail as part of our knowledge warehouse.
We have encountered an error which has stumped our conversion.
We are getting an M3 535 error stating that "First specify the main EAN for the unit EA". We are using LSMW (IDOC Method, Basic Type ARTMAS05).
Our MARM segments have generic and variants. The UPC and UPC category (set to UC) are filled for the variants and blank in the segment containing the generic.
Our MEAN segments contain variants only with the UPC and UPC category (set to UC) filled.
Our UC EAN category is configured with a blank check digit algorithm and a number range of 12 digits. We are loading our variants with EANs that are 12 digits.
When debugged IDOC_INPUT_ARTMAS, I noticed that :
In routine MARM_UEBERGEBEN (in function module BAPI_MATERIAL_MAINTAINDATA_RT), this code clears our MARMX indicators :
   LOOP AT UNITSOFMEASURE.
    ART_DATA_EXISTS = 'X'.    "JH/05.01.00/4.6C Entkopplung der MALG
    IF UNITSOFMEASURE-FUNCTION NE C_MSGFN_D.   ->>>> this checks if our function code is 003 (which is a delete).
*     TMFIELDRES aufbauen
      CLEAR UNITSOFMEASUREX.                   ->>>> Since we are doing a create, it clears the indicators in unitsofmeasureX
To bypass this clear, I debugged the program and overlayed the indicators and marked UPC and UPC category as 'X'. This worked and we were able to post our IDOC successfully... THe UPCs showed in the MARM and MEAN tables.
However, knowing that there are a lot of Retail companies loading articles into their SAP system, it would seem odd that no one has reported this as a bug or no one has posted this issue in SDN. I could not find any OSS note related to this issue either.
Can you please help us figure out what is wrong ? Have you encountered this error in the past ? Is there something in config that we should check ? Should we look at fields in our segments ?
Any help from you would be greatly appreciated.
Thanks,
Sarah

Dear Sarah,
please open an OSS customer message.
Put in a valid IDOC ARTMAS number with this error and open your system.
I guess either it is a bug in IODC structure or you found a bug in software.
My colleages will take care.
Regards
Björn

IDOC type for Article Master : IS Retail

Hi all,
I am new to ALE/ IDOC and working in a scenario to create article master in SAP from third party application. The client is using IS Retail system with ECC 6.0. Can you please suggest what IDOC type to be used. The IDOC will be sent to SAP system from the third-party application. The IDOC can then be processed to create article master. Is ARTMAS the right message type for it? Somebody also suggested using message type WP_PLU. Can someone please let me know what is the difference between them?
Thanks,
Sonika

Hello Sonika,
WE_PLU is generally used along with the POS interface.
Please check this for more details
http://help.sap.com/saphelp_470/helpdata/en/ed/df673c86d19b35e10000000a11402f/frameset.htm
Article Master Uploading in IS- Retail system
This is basically your call depending on what data the message type is intended to carry and the use. ARTMAS should be the choice in your case.
Regards,
Nimish

Material Master MATMAS IDOC and base unit of measurement

Hi
We are using SAP standard material master IDOC type MATMAS05 to trigger IDOC. Our material master is having base unit of measure as "G". We are not using ISO unit of measurement. But Material master IDOC, segment E1MARM is populating base unit of meaurement (MEINS) as "GRM".
Any idea why IDOC is picking ISO unit of measurement instead of material master base unit of measurement.
Any idea how to send base unit of measurememt as "G" instead of "GRM" in DOC segment.
Thanks
Nilesh

There are ISO codes for country keys, currency keys, units of measure and shipping instructions. According to SAP design guidelines, you should use ISO codes for an IDoc if they are available. When you set up the IDoc, the SAP codes have to be replaced by ISO codes.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf

BAPIs for IS-RETAIL Article Master data.

Hi frnds,
I need a standard Bapi to display all existing merchandise categories( material grp), article type(material type) when executing without giving any input parameters.
Regards,
Krishna.

Hi Kumar,
Go to MM41, enter your article A1 and vendor 1.Select purchasing view then enter your purchasing group and purchase price for that vendor1 and save it.Again go to the same purchasing view and click validity area, you will get a pop up box where u can enter
your vendor 2 enter your purchasing group and purchase price of vendor 2 then save it.Do the same for yr other 3 vendors.

Difference b/w Master & Communication IDocs

Hi All,
What is the difference b/w Master & Communication IDocs.
Akshitha.

The master Idoc is the Temporary Idoc & kept in memory buffers until communication IDocs are generated. These recipient-specific IDocs are called Communication IDocs and are Stored in the Database.
But the master Idoc is not.
The Communication IDocs are transferable IDocs not the Master Idoc. For every Receiver, each separate communication Idocs will be created from master Idoc.
more info on idocs....
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
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.
Try this..Hope this will help.
SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
Check 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://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
Please check this PDF documents for ALE and IDoc.
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
Regards
vasu

Master& communication idocs

if i send an idoc to 5 recipents how many master & comunication idocs will be generated

1 master and 5 communication idocs.

Transfer article master from SAP R/3 To External Systems(Futura) Using IDOC

Dear Experts
Please let me know how to Transfer article master from SAP R/3 To External Systems(Futura) or text file Using IDOCs.
thanks

Hello,
Since you want to transfer Article Master, it should be a Retail System. So you should use Message Type ARTMAS. For fullbuild, you can use transaction WDBM and for changes, you can use WDBU. For changes, you can enable change pointers for required fields using BD64.
Thanks,
Venu

Outbound IDOC for Article Master in WPMA without Price

Hi,
How to Generate an Outbound IDOC for Article Master in WPMA Tcode without maintaing Price for the Article. Please suggest Is it Possible in IS-Retail. If so, what needs to be Done.
Regards,
Selvakumar. M

Hi Selvan
In patner profile of outbound, Assign WP_PLU01 instead WP_PLU03..
This will solve ur problem
Regards
Vijai Jain

Article Master Uploading in IS- Retail system

Hi Experts,
Please tell me what are the steps in Uploading Article Master in IS Retail system during GO Live???
How to convert Articles in Legacy system to SAP system (Whether we need to change number range (Internal or External) of Article Type during Upload time???)
We need to extend each variant of generic article for purchasing, sales, logistics DC and Store View since each variant article is brought at different price in Different DCu2019s. (Once we create Generic article, then only we will come to know the variant codes u2013 How to handle this scenario during GO-Live)
Can any one tell me, how these activities are generally handled in IS-RETAIL Project???
Any Input is highly appreciated.
Thanks and Regards,
Selvakumar.M

Uploading articles should be done in all cases always with IDOC type ARTMAS
Converting can be done with migration workbench LSMW
Number ranges can be internally or externaly. It doesnt matter in migration.
If you plan to use internal numbers for article numbers, then define a numberrange
set the counter higher than your current number of articles.
Migrate the articles in the created number gap range.
Please do not mix up master data and prices.
With ARTMAS you can migrate the views and pure master data. I recommend to use the WRKKEY fields at the end of the IDOC to speed up processing.
Always don't forget to define REFRENCE DC and REFERENCE STORE setting in customizing. Article master will work only if these settings are correct.
To simplify process, create manually some reference articles. That helps a lot.
For all other things or hints, we need more details.
It can be very easy up to very sophisticated. The artcicle master is a nice piece of software, very flexible, but also very bad, if you use it by a wrong way.....
Cheers
B

SAP MDG and article master in SAP IS-Retail

We need a solution, where external vendors can contribute with article information, the master data persons can enrich the vendor information, and where the articles can be created appropriately afterwards in SAP ERP.
SAP Master Data Governance (MDG) seems to be the right solution for standard SAP. And SAP MDG has also been described in enhancement packages for SAP Retail since at least ECC 6.05, Nevertless previous discussions such has MDG-Material and IS-Retail indicate that SAP MDG is not appropriate for SAP Retail.
Please contribute with your considerations and experiences: Is MDG appropriate for article master data maintenance in SAP Retail?

Hi Sune
The thread you are refering to is quite old, there is a solution available now for doing retail master data governance on SAP MDG. This is offered as a consulting solution now.
The data model itself is modelled after the IS Retail data model for Article master and would leverage on the data governance capabilites offered by the MDG framework.
It is not exactly a supplier portal for data exchange but there have been architecture discussions on using a 'lean' version of the data model as a vendor facing portal and seperating this from internal facing MDG for enriching the ERP specific parts of the article master data , before governing and commiting to the ERP system.
If you are interested in talking more about it would be happy to do so.
Regards
Dilip

User exit; Article master SAP Retail for MVKE table?

Is there a user exit in SAP Retail for the MVKE table?
The articles is maintained in a third-party system and are transferred to SAP via Idoc. For sales sets, article category = 10, these requires a item category = ERLA in SAP (MVKE-MTPOS) so that the sales set "explodes" in the sales order.
The third-party system doesn't maintain sales org-spesific data for the articles, therefor we use one ref.article for all article groups. And because sales sets exits in many article groups, we found it difficult to have ref.articles for all of these article groups.
Also the article type is also "normal",so the only way to differentiate the sales sets, are via article category. But since SAP has no link between article category and item category in customizing (as far as I know), I wonder if there is a user-exit to set the item category based on the article category?

Hello Sonika,
WE_PLU is generally used along with the POS interface.
Please check this for more details
http://help.sap.com/saphelp_470/helpdata/en/ed/df673c86d19b35e10000000a11402f/frameset.htm
Article Master Uploading in IS- Retail system
This is basically your call depending on what data the message type is intended to carry and the use. ARTMAS should be the choice in your case.
Regards,
Nimish

Article Master Data Extraction from IS-Retail System

Hi,
I have one IS-Retail System with me. I want to extract Article Master data from IS-Retail System.
Is there any specific procedure to do this? If yes, can anybody tell me the procedure?
Waiting for your response...
Cheers,
Yash K

Hi Yash,
you can use transaction BD10 to extract articles. Note that you should change to message type "ARTMAS" instead of "MATMAS".
Best regards
Michael

Asking for help about modification to article master data of retail system

Deal All,
Is there any one can tell me how to modify the article master data in retail system ?
I have tried to deal with the requirement by BDC and calling the function BAPI_MATERIAL_MAINTAINDATA_RT,
but both of the two approaches can not update the customized fields in the table MAW1.
For BDC, the changed data can only be update in debug mode.
For the function, no customized fields of table MAW1 are taken into account as to its parameters.
Can anyone tell how I should do ?
Thanks in advance,
Kevin

Hi Kevin,
Try FM: MATERIAL_UPDATE_ALL_RETAIL
Thanks,
Dharmishta

Transfer Material Master (MATMAS) Idoc into Retail Article Master (ARTMAS)

Similar Messages

Maybe you are looking for