Tag Archives: SAP article

SAP mm receives the purchase order and reports an error – table t169p entry znmi does not exist-

SAP mm receives the purchase order and reports an error – table t169p entry znmi does not exist-

The following purchase order 4500000754,

Execute the transaction code Migo. For the receipt of 101, the error is reported as follows:

Error message: table t169p: entry znmi does not exist

Znmi is a newly created company code. This error is likely to be missed in some configurations.

Se12 look at this t169p table,

It seems that something related has been omitted. After investigation, the following configurations need to be completed:

Maintain a new entry, as shown in the figure above.

Then there is data in t169p table, as shown in the following figure:

Try Migo receiving again and it will be successful!

-Finish-

Written on November 15, 2021

SAP RETAIL Automatic replenishment WRP1R transaction code error: Forecast values for determining target stock do not exist –

SAP retail auto replenishment wrp1r transaction code error – forecast values for determining target stock do not exist-

The MRP type is RF

The material has no inventory,

Execute automatic replenishment transaction code wrp1r,

Error: EWT 131 forecast values for determining target stock do not exist, as shown in the figure above.

The reason is that the forecast data is not maintained for materials. MM42 modifies the master data,

Click the forecast values button,

Maintain forecast data by week and save.

If you execute the transaction code wrp1r again, you will no longer report an error,

Successfully triggered the replenishment order!!!

SAP RETAIL WA01 Creative Distribution List Error – Plant 0000000039 Confirmation date not maintained. –

SAP retail wa01 create allocation report error – plant 0000000039 confirmation date not maintained-

In SAP retail system, try to execute transaction code wa01 to create an allocation table,

Allocation table type z007, purchase organization 0002, purchase group 001.

Press enter to enter the create allocation table interface, enter relevant data and click Save to get the following error reports:

Error report: plant 0000000039: confirmation date not maintained

terms of settlement:

Select item and click the button

, enter the following interface,

Select the first item and click the button,

, enter the following interface,

In the control tab, select d after the request date field, and then enter a date. Then click the message button,

Maintain an output message and click the communication method button to enter the following interface,

Specify a local destination, such as LP01, as shown in the figure above.

Back, back.

Process the remaining items in the same way.

Finally, in the following interface, select item and click Check,

No more mistakes. Now you can save the allocation table data,

Click save,

The allocation table is successfully created as you wish!

-Finish-

2021-11-4 written in residence.

SAP Migo 101 receives the work order and reports an error – check table tfbefu_ CR entry 10 does not exist – Countermeasures

SAP Migo 101 receives the work order and reports an error – check table tfbefu_ CR entry 10 does not exist – Countermeasures

Execute transaction code Migo, move type 101, perform receipt posting for a work order, and the system reports an error: check table tfbefu_ Cr: entry 10 does not exist

F1help documentation:

Check table TFBEFU_ CR: entry 10 does not exist

Message no. M7001

Diagnosis

In table TFBEFU_ CR the entry 10 is missing.

Procedure

Make sure your entries are correct.

If table has not been maintained correctly, please inform your systems administrator.

This error report is the first time I have encountered it, so I am very curious and hope to find out the reason. It is found that the background configuration of a co module is missing, and the transaction code is opk9. The configuration path is as follows:

You need to add an entry to this configuration for the factory code corresponding to the work order. After configuration, you can post the work order receipt normally.

-Finish-

Written on October 12, 2021

On the usage of ‘ref.stor.type search’ field in SAP WM movement type

SAP WM Movement Type   On the usage of ‘ref.stor.type search’ field in

The author is responsible for the implementation of mm and WM in the current project. According to the current situation of the storage area of the customer warehouse, I have enabled the following storage type in the design of storage type at the WM level:

001: high level storage area of raw materials

005: fixed shelf storage area for raw materials

PBL: isolation area beside the production line (production red area)

Qbl: quality isolation area (quality red area)

As well as self-made semi-finished products and finished products storage area.

The storage type indicator is enabled when the raw materials are delivered,   There are different indicators for different types of materials, so that when these materials are put on the shelf or removed from the shelf, the system can automatically suggest that they be put on the shelf or removed from the shelf in the specified storage area.

For example, when some raw materials are removed from shelves for production preparation, they are first delivered from 001 and then delivered from 005;

When some raw materials are removed from shelves for production preparation, they are first discharged from 005 and then from 001. According to these requirements, I have completed the relevant configuration in storage type search.

When business departments need to isolate materials for some reason, they need to move the materials to PBL and qbl. If judged by the quality department, these isolated materials need to be scrapped. At this time of shipment, when the business does not want to issue from to in this scrap scenario, the system recommends to issue from 001 or 005 by default, but requires the system to automatically recommend to issue from PBL and qbl.

To achieve this requirement, you can enable ‘ref.stor.type search’ in WM mobile type settings. That is to say, for the same material, different storage types are recommended for different business scenarios

Then, in the configuration of storage type search, add the following configuration items:

Of course, the premise is that when you search for storage type, you should consider  ‘ Ref.storage type search ‘, as shown in the following figure:

This completes mb1a + 555 at the front desk   After the mobile type scrap issue, when lt06 is executed to create to, the interface will automatically suggest that the business be transferred from PBL & amp; In qbl:

In other scenarios, for example, when the goods are delivered to the cost center, the system will issue the goods from 001/005 and other storage areas according to the normal delivery strategy

2016-12-01   Written in Wuhan Economic Development Zone

SAP MM41 error: Retail materials cannot be maintained.

SAP MM41 error: Retail materials cannot be maintained in the industry system

Trying to execute transaction code MM41/MM43, I received the following error.

Retail materials cannot be maintained in the industry system
Message no. MH194
Diagnosis
Your system is not defined as an SAP Retail System. For this reason, you can use only industry functions for maintaining material master records, and not retail-specific maintenance functions.
Procedure
Contact your system administrator.

The analysis of the reported error is as follows.

To use the Retail-transactions you need to have your system set to Retail – with all the advantages and restrictions of Retail. And: there’s no turning back to a normal system unless you reinstall it.
So, to set up Retail, go to SPRO -> Activate SAP ECC Extensions -> Choose Industry Business Function Set ISR_RETAILSYSTEM. Again: once you activate the Business Function, you CAN’T go back – unless you wipe the whole system.
Please also read the SAP Help on SAP Retail to get familiar with the solution BEFORE you activate it. I think it’s lot less trouble than reinstalling the system.