fbpx

Conversion ExitUnderstanding Internal Characteristic Numbers (ATINN)

by

CABN (Characteristic Master) uses field ATINN as the internal characteristic number and ATNAM as the external characteristic name.

 

When working in SE16/SE16N, SAP may display or require the internal characteristic number (ATINN) instead of the business-friendly characteristic name (ATNAM). The characteristic values stored in classification tables such as AUSP are linked using this internal number. To identify the actual characteristic, you need to map ATINN → CABN-ATNAM (Characteristic Name) or CABNT-ATBEZ (Characteristic Description)

Example:

 

Internal Number (ATINN) Characteristic Name (ATNAM)
0000001234 COLOR
0000005678 ENGINE_TYP

Therefore, when analyzing classification or variant configuration data in SE16/SE16N, the displayed value may be the internal characteristic number (ATINN) rather than the characteristic name. In such cases, refer to table CABN to translate the internal number into the corresponding characteristic name. CABN stores both the internal characteristic number (ATINN) and the characteristic name (ATNAM)

This conversion exit is available in the SE16N > Extras > Change Setting >

⚡ One-Click in PMEVC: Release + Save Dependencies Instantly!

by

Loading

SAP has introduced a small but powerful improvement in PMEVC — a new toolbar button that lets you release and save a dependency in a single click. This gives a  Cleaner navigation experience in PMEVC  and Reduced clicks + Time saving No more jumping to the Basic Data tab. No more extra navigation. Just clean, fast modeling!

 

🔍 What’s New? (Simplified)

🆕 New toolbar button

  • Release + Save dependency at once

Works for both:

  • 🔸 Local dependencies
  • 🔸 Global dependencies

⏱️ No more tab switching

  • Skip the Basic Data tab completely
  • Smoother, faster modeling
    workflow

💡 Perfect for AVC consultants working with frequent dependency updates.

 

 If you work with dependencies daily, activate this note and upgrade your modeling speed instantly.

Need help refining dependencies or optimizing AVC design? Feel free to reach out!

Note:  3486340 – PMEVC: Release and save dependency at once

 

#SAPAVC #VariantConfiguration #SAPS4HANA #PMEVC #SAPDependency #SAPConsulting #AVCExpert #SAPManufacturing #SAPTips #SAPNote

 

 

 

🚀 PMEVC: Download Variant Tables with Multi-Value Cells!

by

Loading

Great news for all AVC modelers and PMEVC users — SAP has enabled downloading variant tables even when they contain multi-value cells, thanks to SAP Note 3547198. This removes one of the biggest limitations in variant table handling.

🔍 What’s New? (Simplified)

📥The variant table content is downloaded as an xlsxfile.

 📄Values contained by multi-valued entries are downloaded with a line break as a seperator.

 🔢Numeric values are converted from user setting format to internal format, e.g., 1.234,567 -> 1234.567, 300,0000E-06 ->

0.0003.

 ✨If available, wildcards in variant tables of processing mode ‘Advanced Variant Configuration’ are downloaded as blank cells.

 🖥️The characteristic values are downloaded depending on the selected display setting in PMEVC, i.e. values or descriptions. In case of display setting ‘Descriptions’, only characteristic value descriptions are downloaded as such, characteristics will still be displayed as value.

  💡 Why This Matters

Faster copying,
editing, and validating large variant tables

➜ Better performance, less manual clean-up, and improved model quality.

If you work with AVC tables, implement SAP Note 3547198 and
start downloading your variant tables without restrictions. Need help optimizing your AVC setup? Reach out — happy to guide you!

#SAPAVC #VariantConfiguration #SAPS4HANA #PMEVC #SAPConsulting #SAPManufacturing #SAPFunctional #SAPTips #SAPNotes #AVCExpert

🚦 SAP S/4 HANA – AVC: Now You Can Edit the Restrictable Flag!

by

A small improvement for anyone working with PMEVC and characteristic modeling in SAP S/4HANA. SAP now allows changing the Restrictable flag for

existing characteristics — with important conditions.

🔍 What’s New?

  • ✔️ The Restrictable flag is now editable after characteristic creation
  • ✔️ By default, PMEVC sets the flag as Restrictable when creating characteristics
  • ✔️ Previously, this was locked and couldn’t be modified later
  • ✔️ SAP Note 3645148 now enables the change — but only when conditions are met

✅ Conditions to Modify the Restrictable Flag

 

  • 🔸 The characteristic is NOT used in any released dependency
  • 🔸 Additional Values is NOT active in the value domain

📌 Reference: SAP Note 3645148 – PMEVC: editing of restrictable flag after creation of characteristic

If you’re working on AVC modeling, review your characteristics and check if this update can simplify your current project.

 

#SAPAVC#VariantConfiguration #SAPManufacturing #SAPConsulting #S4HANA #PMEVC #SAPNotes
#AVCExpert #SAPTips #SAPCommunity

How to find the odata errors in SAP S/4HANA

by

Loading

Check OData Error Logs in /IWFND/ERROR_LOG

The primary location for checking OData service errors is the transaction /IWFND/ERROR_LOG.

  • Steps:
    1. Execute the transaction /IWFND/ERROR_LOG in the SAP GUI.
    2. Use filters such as User, Date/Time, or Service to narrow down the results.
    3. Check the error details for further analysis.
  • Error Analysis:
    • Analyze the error codes and messages.
    • Inspect the stack trace for technical details.
    • Often includes information about missing authorizations, incorrect URIs, or payload issues.

Advanced Variant Configuration screen does not open in classic SAPGUI transactions

by

The Advanced Variant Configuration screen does not open in classic SAPGUI transactions (e.g. Sales Order processing) and shows an error page or an empty screen or an error message that some requests were not successful in case the S/4HANA embedded Fiori deployment option is used, which means S/4HANA backend and Fiori frontend server system are the same.

Another issue is that a logon page comes up in SAPGUI for Windows when opening the Advanced Variant Configuration screen in case the S/4HANA embedded Fiori deployment option is used.

The reason for the issue in the Advanced Variant Configuration screen is that an origin URL parameter is added to the OData requests sent to the SAP Gateway system, which is prohibited by SAP Gateway in the Co-Deployment scenario.

The logon page issue happens because in SAPGUI for Windows, the SSO logon cannot be established the same way as when accessing the system via Fiori Launchpad and embedded SAPGUI for HTML; instead, a ticket-based logon using special capabilities of the SAPGUI HTML Viewer control is used.

Refer the Notes: 2916536-2916536 – SSO and OData Issue Fix for Advanced Variant Configuration

 

Characteristic results cannot be recorded for inspection lot: Message no. QE181

by

Loading

Generally if there are some master data issues then we will get the below error message during the Inspection Lot Generation.

Characteristic results cannot be recorded for inspection lot 1000xxxxxx
Message no. QE181

Diagnosis
You cannot record any characteristic results for this inspection lot. The material master has been set up for the existing inspection type in such a way that results recording is not supported.

Procedure
Confirm defects for this inspection lot or select another inspection lot in which you can confirm the characteristic results.

Solution:

  1. Please check if there is a Task List assigned to the Inspection lot.
  2. If not then try to go to the change mode of the inspection lot and try to assign the task list /Spec
  3. Either it will get assigned or it will provide some error messages.
  4. Once you resolve this then the next inspection lot should get the Task list automatically

Also note the easy way of identifying this issue is by using the Inspection lot status. The below comparison will help you .

Automatic generation of inspection lot failed

by

Loading

During the Inspection lot generation especially the 03 lots are not getting generated and below message are noticed:

  • Inspection lot not created automatically via transaction CO01/CO02
  • Warning message CO548 raised in production order release
  • Production order has status ILNC – Inspection lot not created
  • Warning raised in production order release – ‘Material &1: automatic generation of inspection lot failed’

The below message is displayed:

Material XXXXXXXXX: automatic generation of inspection lot failed

Message no. CO548

Diagnosis

The system tried to create an inspection lot, but failed.

System Response

Processing is continued without creating an inspection lot.

Procedure

Check, whether the quality inspection data is maintained in the material master.

When you have maintained all the necessary data, you can also create the inspection lot in a production order / process order at a later date by calling up the screen ‘main header’ again.

Solution:

  1. Refer the Note https://me.sap.com/notes/1798998
  2. as per the note kindly activate the user exit EXIT_SAPLQPL1_005 in enhancement QAAT0001 and manage the code E_TQ32 = I_TQ32
  3. This will resolve the Problem