SAP software development

Target Group  SAP PP User and IT Professionals

Summary

The BOM Browser with Master Data Check got even better 🙂

Content

My Add-On BOM Browser with Master Data Check meats considerable customer demand and I implemented enhancements:

  • Multi-plant selection
  • Optional cross-plant BOM explosion. Stock-transfer via special procurement key is treated similar to an extra BOM level. The BOM explosion proceeds in the supplying plant.
  • Display plant stock
  • Visualization of phantom assemblies, subcontracting, stock transfer and regular in-house production with icons
  • MRP Area specific BOM explosion via production version determination and storage location determination
  • Separate counters for WM control cycles and Kanban control cycles
  • Additional report for material evaluation with master data check without BOM explosion. This report contains more material data and is ideal for fast and flexible material evaluation with focus on checking PP/MM master data and viewing material details.
  • Settings for reaction on missing production version or source list: Error, Warning or No Reaction
BOM Browser with Master Data Check – Tree View
BOM Explosion with Plant-to-Plant-Stock_Transfer
Visualizing different types of assemblies: Subcontracting, Phantom Assemblies, Stock Transfer, Normal Inhouse-Production

You find more info here.

I’m looking forward to comments and questions.

Do the SAP standard transactions for mass evaluation of BOMs satisfy your requirements?

How robust is your workflow for creation and maintenance of materials and related master data for production and procurement? How useful would be a mass evaluation of materials with existence information (in form of counters) for assigned master date (routings, BOMs, source list, infor records, control cycles, production versions) for you?

Would you see the benefit of using the BOM Browser with master data check mainly in

  • Master Data Mangement for checking existence of critical master data?
  • In Product Costing for viewing multi-level BOM structures across plants, with plant stock and valuation data?
  • In Logistics, e.g. for monitoring stock in BOM structures or checking existence of WM or Kanban control cycles?
  • In Production Planning as an overview of BOM structures with stock and MRP parameteres. Maybe enhanced with coverage data or summarized requirements and receipt

Do you have ideas for other use cases or improvements?

Download and Upload ALV Layouts

Target Group

SAP Professionals, SAP Key User

Summary

Free report for downloading and uploading ALV Layouts. The report is available on github.

Motivation

The SAP standard allows to transport user independent ALV layouts and to copy ALV layouts to another client in the same system.

However it sometimes happens that you can’t transport to the system where the ALV layouts are needed. I haven’t found a solution for this with SAP standard transactions or via business configuration sets. Internet searches returned some coding fragments which only helped to a small degree.

So I developed a report and provide it free of cost with the so-called MIT Licence via Github.

The report is implemented in an old-fashioned way without using any newer ABAP elements in order to support all usual releases of SAP ERP and S/4HANA. I tested it in ERP 6.0 releases with SAP APPL 6.05 and 6.17 and in S/4HANA 2020 with S4CORE 105. Original language is English, with German translation.

Use Cases

  1. Copy user dependent or independent ALV layouts from one SAP system to another. The systems can have different releases.
  2. Backup and restore ALV layouts.
  3. Copy ALV layouts from one report to another, e.g. after copying or renaming a customer development.

Documentation

Report ZST12_ALV_LAYOUT_UP_DOWNLOAD asks for a report name, a local path name and the choice between download or upload.

Download – Export to local files

All layouts for the report are proposed for download. User dependent layouts are included. You see all existing ALV layouts even if the report uses multiple ALVs with different HANDLE keys.

Field catalog, layout setting, language dependent short texts, sort and filter criteria (if existing) are exported in separate files. The file names are generated automatically.

(1) Selection screen – Download
(2) Popup to select layouts for download
(3) Download Protocol

Upload – Import from local files

The downloaded layouts in the specified folder are proposed for upload to the target report. Source report, source system, layout ID, layout description and download date are automatically determined from file name and content.

(4) Selection Screen – Upload
(5) Popup to select layouts from the local folder for upload
(6) Option to put uploaded layouts in a transport
(7) Upload protocol

Restrictions

  • The imported layout overwrites an existing layout without warning
  • No consistency check when importing layouts to another report
  • No existence check for the user if you import a user dependent layout
  • Currently no function to import a user dependent layout to another user

Coding

The current version is available on github. You can download it with abapgit, other git clients or manually:

www.github.com/Martin-Preiss/SAP_ALV_LAYOUT_DOWNLOAD_UPLOAD