Hello all,
While trying to create Generic Articles master using LSMW idoc ARTMAS05, I am getting an error message 'The generic article could not be created as a class'. I am trying to create 2 variants and have filled up the corresponding characteristics segment. I am able to do it manually using MM41.
Any help appreciated.
Thanks
Anmol
Hi experts,
We use correction DIF in Forecasting and Replenishment module while generating forecast. From last one week when we just hit enter after selecting the DIF ID = COR (happens with any other DIF ID). the information message is pooped up: '0000000254 already exists'. If you go to the /FRE/DIF_OCCURR table, you will see that the DIFN 254 does not exist. Also does not seems an authorization-check problem. Also checked if there was some table locking and there was no locking. So not sure how to correct this.
Thanks & Regards
Yogeesha
Summary Reports :
They contain details about transactions like sales, discount, refund.
Under this category we have the following BEX reports :
Refund Summary Report
Overshot Summary Report
Transaction Snapshot Summary Report
Sales Summary
Post Void Summary
Transaction Discount Summary
Item Discount Summary
Exception Reports :
These reports contain information regarding one or more exception templates. These exception templates are preprocessed patterns which help to recognize fraudulent activities.
For more on exception templates please refer to http://scn.sap.com/docs/DOC-54917
The BEX exception reports are :
Report Card Report - It contains information on more than one pattern on a higher level.
Exception Report - Contains information about one particular pattern.
Lookup Reports :
Under this category we have
Cashier Lookup - Contains information about a particular cashier.
Credit Card Lookup - Contains information about the transactions done using credit cards.
In addition to these reports we also have the transaction viewer and the journal viewer.
Transaction Viewer
It contains the details of a particular transaction like header, line item, loyalty, discount. The view of the report can be changed from the cashier to POS number. You also have an option to navigate to the Journal Viewer.
Journal Viewer
This report is used to view the surrounding transactions done by the same cashier or from the same POS register within a stipulated period of time frame
It can be opened from the transaction viewer or can also be used as a stand alone report. Since its a web dynpro component it can be called up from any application as well.
When opened from the transaction viewer, it picks up the parameters like posting date and store id from it.
It displays the list of transactions performed at the same POS register or the same cashier for a single day. The minimum parameters are date, store id.
The selection criteria can be changed after loading the report in the selection criteria area.
The Active pattern column indicates that the transaction is suspicious as per one of the active patterns. It displays the sales movement, goods movement, financial transactions, etc.When you click on a transaction number it navigates to the transaction viewer.
Dear all,
I would like to have basic information about SAP retail.
1. Is it addons for SAP ERP or is it completely different from SAP ERP?
2. Does it have point-of-sale implementation feature?
Thank you very much for your help.
Best regards,
Viktor
Hi,
My question is about GTM but i didn't found any specific discussion group about Global Trade Management
With WB21 we have created a trading contract for stock transport order (cross-company)
After that with TEW we didn't found the way to create the outbound delivery for the stock transport purchase order
(We were able to create the good receipt with TEW and now, of course, we get a negative stock in transit (MB5T))
Do you know the way to create an outbound delivery in shipping plant for stock transport purchase order with TEW .? (what is the task (group/step/mode/previous) to use in TEW)
Thanks for Help
Hello Experts,
our customer is using seasonal procurement was well as standard procurement.
For the standard the purchase orders will be created by transaction ME21N. In the seasonal procurement the transaction WPOHF4X is used.
In the pricing procedure the standard condition type MVK0 is used.
In case of ME21N, the condition type is handled properly, however in WPOHF4X is not set in case of new pricing.
There is no adequate SAP note regarding this issue.
Is this an known issue? Is there any solution?
Thank you very much for your assistance.
Best regards,
Kurt
Dear All,
We are trying to access mobile inventory management on handheld device but we are getting the below error.
Device - Intermec
Error - your browser or program is not supported by webdynpro
Link - hostname:50200/webdynpro/dispatcher/sap.com/is~isr~srs~men~app/MainApp
Can any one please help.?
Hi SAP Guru´s,
Currently we are sending the pricing, promotions & article master data delta load to 3rd party system from SAP ECC via SAP XI through IDOCS using daily scheduled batch jobs WPMU. IDOC segment - WP_PLU.
Here the issue is the promotion & pricing data are sent to 3rd party system one day before the actual start date.
Eg: Promotion 123456 which has start date as 15/05/2014 & ending on 30/05/2014 & was created & activated on 13/05/2014.
This promotion 123456 is getting triggered from SAP ECC through batch job on 14/05/2014 morning & 3rd party system receives the data on 14/05/2014 & the promotion are getting activated at 3rd party system end on 14/05/2014 itself which actually gets active from 15/05/2014.
Same in the case for Standard Pricing data which needs to be active from 31/05/2014 once the promotion 123456 ends on 30/05/2014.
The standard pricing data gets triggered from SAP ECC on 30/05/2014 through batch job & reaching 3rd party system on 30/05/2014 & getting activate on 30/05/2014 itself.
This creates more issues at the store end as well as affecting business.
We checked at 3rd party system end & they replied that their system considers the updated time stamp & date to activate the prices & it does not considers the actual active from & active to date. They need the data to be sent from SAP ECC on the effective date of the pricing & promotions.
Can any one help me how to change the pricing conditions beign triggered through batch job in SAP ECC based on the actual promotion & pricing conditons start date or is there any other process to trigger the data through the batch job on the actual promotion & pricing data activation date.
Thanks in Advance.
Thanks & Regards,
P.P.Shankar
Article Master – LSMW – Generic/Variants - ARTMAS05
This subject raised a few questions in an SCN thread with the title of Error while trying to create Generic Articles with variants using LSMW (ARTMAS05).
A document that I wrote in response to that question is requested frequently. This post replaces the document named md_article_generic_lsmw.pdf
Creating a generic article master with variant articles is accomplished via processing of one ARTMAS05 IDoc.
There is important prerequisite master data, which is detailed in steps below that were executed to create an example.
| PROCESS STEP | PROCESS STEP IMAGE |
|---|---|
CT04 – Create Characteristic
Create HN_COLOURS |  |
CT04 – Create Characteristic
Maintain values for HN_COLOURS |  |
CLWE – Create Characteristic Profile
Create HN001 |  |
CLWE – Create Characteristic Profile
Assign Characteristic and make relevant for the creation of Variants. |  |
WG21 – Create Merchandise Category
Create S14 |  |
WG22 – Change Merchandise Category
Change S14
Assign Characteristic Profile HN001 |  |
WG22 – Change Merchandise Category
Change S14
Create reference article. |  |
WG22– Change Merchandise Category
Create reference article A11000011. Maintain all views except Purchasing. |  |
LSMW – Process ARTMAS05
|  |
LSMW – Process ARTMAS05
|  |
LSMW – Process ARTMAS05
|  |
LSMW – Process ARTMAS05
|  |
MM43 – Display Article Click the Variants button to display the Variants. |  |
| MM43 – Display Article |
|
Here is the IDoc that created the example Article Master
Observe the usage of segments and fields.
| SEGMENT | FIELD NAME | SHORT DESCRIPTION | VALUE |
|---|---|---|---|
| E1BPE1MATHEAD | FUNCTION | Function | 009 |
| E1BPE1MATHEAD | MATERIAL | Article Number | A11000010 |
| E1BPE1MATHEAD | MATL_TYPE | Article Type | HAWA |
| E1BPE1MATHEAD | MATL_GROUP | Merchandise Category | S14 |
| E1BPE1MATHEAD | MATL_CAT | Article Category | 01 |
| E1BPE1MATHEAD | CHAR_PROF | Characteristic profile | HN001 |
| E1BPE1MATHEAD | REF_MATL | Reference article | A11000011 |
| E1BPE1MATHEAD | BASIC_VIEW | Include Basic Data View | X |
| E1BPE1MATHEAD | LIST_VIEW | Indicator: Consider Listing view | X |
| E1BPE1VARKEY | FUNCTION | Function | 009 |
| E1BPE1VARKEY | MATERIAL | Article Number | A11000010 |
| E1BPE1VARKEY | VARIANT | Variant number | A11000010001 |
| E1BPE1VARKEY | FUNCTION | Function | 009 |
| E1BPE1VARKEY | MATERIAL | Article Number | A11000010 |
| E1BPE1VARKEY | VARIANT | Variant number | A11000010002 |
| E1BPE1AUSPRT | FUNCTION | Function | 009 |
| E1BPE1AUSPRT | MATERIAL | Article Number | A11000010001 |
| E1BPE1AUSPRT | CHAR_NAME | Characteristic Name | HN_COLOURS |
| E1BPE1AUSPRT | CHAR_VALUE | Characteristic Value | 10 |
| E1BPE1AUSPRT | FUNCTION | Function | 009 |
| E1BPE1AUSPRT | MATERIAL | Article Number | A11000010002 |
| E1BPE1AUSPRT | CHAR_NAME | Characteristic Name | HN_COLOURS |
| E1BPE1AUSPRT | CHAR_VALUE | Characteristic Value | 20 |
| E1BPE1AUSPRTX | FUNCTION | Function | 009 |
| E1BPE1AUSPRTX | MATERIAL | Article Number | A11000010001 |
| E1BPE1AUSPRTX | CHAR_NAME | Characteristic Name | HN_COLOURS |
| E1BPE1AUSPRTX | CHAR_VALUE | Updated information in related user data field | X |
| E1BPE1AUSPRTX | FUNCTION | Function | 009 |
| E1BPE1AUSPRTX | MATERIAL | Article Number | A11000010002 |
| E1BPE1AUSPRTX | CHAR_NAME | Characteristic Name | HN_COLOURS |
| E1BPE1AUSPRTX | CHAR_VALUE | Updated information in related user data field | X |
| E1BPE1MARART | FUNCTION | Function | 009 |
| E1BPE1MARART | MATERIAL | Article Number | A11000010 |
| E1BPE1MARART | OLD_MAT_NO | Old article number | 9999MAT |
| E1BPE1MARART | BASE_UOM | Base Unit of Measure | EA |
| E1BPE1MARART | TRANS_GRP | Transportation Group | 0001 |
| E1BPE1MARART | DIVISION | Division | 10 |
| E1BPE1MARART | TAX_CLASS | Tax classification of the article | 1 |
| E1BPE1MARART1 | BRAND_ID | Brand | 0001 |
| E1BPE1MARARTX | FUNCTION | Function | 009 |
| E1BPE1MARARTX | MATERIAL | Article Number | A11000010 |
| E1BPE1MARARTX | OLD_MAT_NO | Updated information in related user data field | X |
| E1BPE1MARARTX | BASE_UOM | Updated information in related user data field | X |
| E1BPE1MARARTX | TRANS_GRP | Updated information in related user data field | X |
| E1BPE1MARARTX | DIVISION | Updated information in related user data field | X |
| E1BPE1MARARTX | TAX_CLASS | Updated information in related user data field | X |
| E1BPE1MARARTX | BRAND_ID | Updated information in related user data field | X |
| E1BPE1MAW1RT | FUNCTION | Function | 009 |
| E1BPE1MAW1RT | MATERIAL | Article Number | A11000010 |
| E1BPE1MAW1RT | REPL_LIST | Assortment List Type | 1 |
| E1BPE1MAW1RT | ABC_ID | ABC Indicator | A |
| E1BPE1MAW1RT | PUR_GROUP | Purchasing Group | 100 |
| E1BPE1MAW1RT | COUNTRYORI | Country of origin of the article | AU |
| E1BPE1MAW1RT | LOADINGGRP | Loading Group | 0001 |
| E1BPE1MAW1RT | ASSORT_LEV | Assortment grade | 1 |
| E1BPE1MAW1RT | LI_PROC_ST | Listing procedure for store or other assortment categories | B1 |
| E1BPE1MAW1RT | LIST_ST_FR | Date from which listed in the store | 20130401 |
| E1BPE1MAW1RT | LIST_ST_TO | Date to which listed in the store | 99991231 |
| E1BPE1MAW1RT | SELL_ST_FR | Date from which sold in the store | 20130401 |
| E1BPE1MAW1RT | SELL_ST_TO | Date to which sold in the store | 99991231 |
| E1BPE1MAW1RT | VAL_CLASS | Valuation Class | 3100 |
| E1BPE1MAW1RTX | FUNCTION | Function | 009 |
| E1BPE1MAW1RTX | MATERIAL | Article Number | A11000010 |
| E1BPE1MAW1RTX | REPL_LIST | Updated information in related user data field | X |
| E1BPE1MAW1RTX | ABC_ID | Updated information in related user data field | X |
| E1BPE1MAW1RTX | PUR_GROUP | Updated information in related user data field | X |
| E1BPE1MAW1RTX | COUNTRYORI | Updated information in related user data field | X |
| E1BPE1MAW1RTX | LOADINGGRP | Updated information in related user data field | X |
| E1BPE1MAW1RTX | ASSORT_LEV | Updated information in related user data field | X |
| E1BPE1MAW1RTX | LI_PROC_ST | Updated information in related user data field | X |
| E1BPE1MAW1RTX | LIST_ST_FR | Updated information in related user data field | X |
| E1BPE1MAW1RTX | LIST_ST_TO | Updated information in related user data field | X |
| E1BPE1MAW1RTX | SELL_ST_FR | Updated information in related user data field | X |
| E1BPE1MAW1RTX | SELL_ST_TO | Updated information in related user data field | X |
| E1BPE1MAW1RTX | VAL_CLASS | Updated information in related user data field | X |
| E1BPE1MAKTRT | FUNCTION | Function | 009 |
| E1BPE1MAKTRT | MATERIAL | Article Number | A11000010 |
| E1BPE1MAKTRT | LANGU | Language Key | E |
| E1BPE1MAKTRT | MATL_DESC | Article Description (Short Text) | QUEEN BED |
| E1BPE1MARMRT | FUNCTION | Function | 009 |
| E1BPE1MARMRT | MATERIAL | Article Number | A11000010 |
| E1BPE1MARMRT | ALT_UNIT | Alternative Unit of Measure for Stockkeeping Unit | KG |
| E1BPE1MARMRT | NUMERATOR | Numerator for Conversion to Base Units of Measure | 1 |
| E1BPE1MARMRT | DENOMINATR | Denominator for conversion to base units of measure | 1 |
| E1BPE1MARMRT | LENGTH | Length | 10 |
| E1BPE1MARMRT | WIDTH | Width | 12 |
| E1BPE1MARMRT | HEIGHT | Height | 15 |
| E1BPE1MARMRT | UNIT_DIM | Unit of Dimension for Length/Width/Height | M |
| E1BPE1MARMRT | VOLUMEUNIT | Volume unit | CCM |
| E1BPE1MARMRT | GROSS_WT | Gross Weight | 1 |
| E1BPE1MARMRT | UNIT_OF_WT | Weight Unit | KG |
| E1BPE1MARMRTX | FUNCTION | Function | 009 |
| E1BPE1MARMRTX | MATERIAL | Article Number | A11000010 |
| E1BPE1MARMRTX | ALT_UNIT | Alternative Unit of Measure for Stockkeeping Unit | KG |
| E1BPE1MARMRTX | NUMERATOR | Updated information in related user data field | X |
| E1BPE1MARMRTX | DENOMINATR | Updated information in related user data field | X |
| E1BPE1MARMRTX | LENGTH | Updated information in related user data field | X |
| E1BPE1MARMRTX | WIDTH | Updated information in related user data field | X |
| E1BPE1MARMRTX | HEIGHT | Updated information in related user data field | X |
| E1BPE1MARMRTX | UNIT_DIM | Updated information in related user data field | X |
| E1BPE1MARMRTX | VOLUMEUNIT | Updated information in related user data field | X |
| E1BPE1MARMRTX | GROSS_WT | Updated information in related user data field | X |
| E1BPE1MARMRTX | UNIT_OF_WT | Updated information in related user data field | X |
| E1BPE1MLTXRT | FUNCTION | Function | 009 |
| E1BPE1MLTXRT | APPLOBJECT | Texts: Application Object | MATERIAL |
| E1BPE1MLTXRT | TEXT_NAME | Name | A11000010 |
| E1BPE1MLTXRT | TEXT_ID | Text ID | BEST |
| E1BPE1MLTXRT | LANGU | Language key | E |
| E1BPE1MLTXRT | TEXT_LINE | Text Line | POS 2nd line description |
| E1BPE1MLTXRT | MATERIAL | Article Number | A11000010 |
| E1BPE1MLTXRT | MATERIAL_EXTERNAL | Long Article Number for MATERIAL Field | |
| E1BPE1MLTXRT | MATERIAL_GUID | External GUID for MATERIAL Field | |
| E1BPE1MLTXRT | MATERIAL_VERSION | Version Number for MATERIAL Field |
--- end of document ---
I would like to know Role of sales organization and distribution channel in WSOA1 basic data tab under control data. Also, if we give default sales area as 3000/10 and we are adding assortment users even belongs to different sales areas.
what is the usage of adding this sales area as default and why does SAP allows assortment users of different sales areas as well.
Hi Gurus,
Kindly suggest me, how can I maintain the serial number for the article after Goods receipt, If the T-code is IQ01 for the same than i am getting the error "
Thanks in advance.
Regards,
Rachana Shah.
Hi all
where i can maintain article hierarchy node number range? I want to create first level with char and create the lower level with pure arabic numerals. but there are only two kinds of number range for article hierarchy node number range. both of them can meet my requirement.
Thanks!
Hi POSDM experts,
We have set up jobs to pick transactions from inbound queue for every 5 mins using the program /POSDW/INBOUNDDISPATCHER. We noticed that certain queues ran into status /posdw/tibq-recordstatus = 2 (error). We can identify the queues in error using /posdw/qmon. (Please be informed we have changed the frequency of the job, it does not matter).
We tried to check for the logs pertaining to the program and found no information. If the queue in error is processed, it is successful and can see the details of the transactions in workbench.
Can you please let us know how to identify the information why they ran into error? Hence determine the fix and avoid the issue.
Thanks,
Suraj Pabbathi
Hi experts
Would you come to know if the transaction/event type (IKPF-VGART) for a physical inventory document (PID) can be configured and changed during a creation of PID? (for example, through BAPI BAPI_MATPHYSINV_CREATE_MULT)
Client requirement is to be able to differentiate different types of PID, and we are trying to look into this field's possibility.
Or if you have other experience on similiar requirement, please also share.
Appreciate your replly
Regards
Dom.
Hello All,
We are considering using SAP AFS for indirect procurement for a customer. Since we have most SAP MM functionality in AFS, ideally it should be fine. But we want to check with the experts on their experiences and challenges if any faced during the same.
Any information will be helpful. Thanks a lot in advance.
Regards,
Shubham
hi all
is there any BAPI or IDOC could be used for assigning article to article hierarchy by lsmw?
Thanks!
We have activated AFS in our ECC 6.0. We are facing the below problem while creating Inbound delivery:
1. While creating the Outbound delivery picking quantity is not coming
2. System is taking automatic batch and it is not allowing us to change the delivery quantity or Batch No. Batch split up tab is not working. We have marked 'X' in valuation category in material master.
Kindly provide us some solution to overcome this issue.
Regards,
P.Jeevanantham
Hi
I am trying to upload Merchandise category and hierarcy using LSMW (BAPI/IDOC method only).
For merhcandise category
I used message type W_WGRP and it is helping me in changing or reclassification of articles. But I am not able to create new merchandise category with this. I used structure E1BPE1WGR01 with "function" field with value "005, LSMW is working fine idocs are created successfully but no new Merc Cat is created.
When I used same structure with "function" field with value "009" I get error message "Class XXX does not exist or or is not valid on this date".
For Merchandise Catrgory Hierarchy
I used idoc CLSMAS but getting error message "Keyword missing for class XXX"
has anybody uploded entire hierarchy structure using LSMW ?
Hi
we have requirement to build the Merchandise category wise GL Accounting in the system that helps to track category wise cost and sales.
I understood in SAP we have Company,Business area ,Cost& Profit center Level GLs for P&L Accounts.
i would like to know is this suggestable to configure the Merchindise category wise GL Accounts. we have arround 1500 Merchandise categories. Mapping 150 GL accounts to the above MCs looks very unwise hence i would like to hear from the experts is this right method to follow or suggest us what can be done better.
Dear all,
I need to find out a way to introduce a second sales price for an article in addition to the standard one. This price has to be lower and is needed when a product can be bought with both money and loyalty card points.
Can anyone tell how such a price can be created and transferred via message type WBBDLD? Condition type VKK0 (promo club sales price) is intended to be used for the purpose of buying with loyalty points but I cannot get a second condition type for a sales price transferred.
Any input will be appreciated.
Thank you!
Regards,
Miro
