quinta-feira, 8 de fevereiro de 2024

Initial stock upload in EWM

 Hi All

For most of the warehouses, the generic requirement is to reflect the stock in newly configured warehouse in the system. So that it matches with the reality. In EWM, we have two ways for this.

1. Create Initial stock in MIGO of ECC (movement type 561). This creates inbound delivery and distributes to ECC. Once the delivery is in EWM, the normal inbound delivery processing steps are followed.

2. Prepare CSV file with all the products/HUs and their quantities. Upload this CSV file into EWM.

In this, I'll explain the process of uploading the initial stock using CSV file.

Useful references for preparing the CSV file:

http://help.sap.com/saphelp_em70/helpdata/en/49/fbcea887c24f47a2518759bd53e5b3/content.htm?frameset=...

Also you can refer SAP Note: 974852 and download CSV file template.

  1. Fill the HU & Product details and save file as CSV file.
  2. Go to TCode: /SCWM/ISU, browse and select CSV file.
  3. Click on Upload button.
  4. Check the uploaded data.
  5. Click on execute button, stock will be uploaded and posted to ERP.


Before:

I have tried to put stock in empty bin “6”. (/n/scwm/mon)

After:

After upload, you'll get a log saying HU is created for material and material document posted. By default "Do Not Post Data in ERP" check box will be unchecked. Because of this, after successful upload, material document posted with 561 movement type.

See below material document posted in ECC after stock upload in EWM.(MB51)

URL given above explains you two variants of stock upload.

1. Without HU

2. With HU (internal or external number range)

Also, good thing about this transaction is (/scwm/isu), after upload you can view the file content in CSV(XLS) format there itself and edit and save the data for upload. Otherwise you can also access the files stored on application server.

Few notes from observations:

1. Packaging specification is not required to defined, to upload stock via CSV file.

2. While uploading more than one HU or Product or both, fields HU, Higherlevel HU(if there are multiple layers in one HU), Highest HU, Line ID must be filled appropriately.

HU - This is unique ID for each HU (a sequence number can be given). For HU, this unique ID should be given and for products inside this should be given. On the same lines, respective HU IDs should be filled for Higherlevel HU and Highest HU.

Line ID is a sequence across rows in CSV.

3. After linking product to HU as above, Storage bin mentioned for Highest level HU will only be considered. If you give different bin for product which even does not exist in the wh, no error will be thrown.

eg:

Item Category,Product,Owner,Partner Role,Batch,Stock Type,Type,Sales Order/Project,Sales Order Item,Usage,Party Entitled to Dispose,Partner Role,Country of Origin,Quantity,Base Unit of Measure,Handling Unit Type,Storage Bin,GR Date,GR Time,Shelf Life Exp. Date,Packaging Material,ExternalNumberAssgmt,Handling Unit,Higher-Level HU,Highest-Level HU,Line ID,Reference to Line,Total Weight,Loading Weight,Weight Unit,Tare Weight,Weight Unit,Total Volume,Loading Volume,Volume Unit,Tare Volume,Volume Unit,Total Capacity,Net Capacity,Tare Capacity Key Fig.,Length,Width,Height,Unit of Dimension,Maximum Weight,Excess Wgt Tolerance,Tare Weight Variable,Maximum Volume,Excess Volume Tol.,Closed,Maximum Capacity,Max. Packing Length,Max. Packing Width,Max. Packing Height,Unit of Measure,Serial Number,Valuation Quantity,Valuation Unit,Valuation Measured,Certificate Number

1,,,,,,,,,,,,,,,E1,BIN3,,0:00:00,,PACKMAT,,1,,1,1,0,,,,,,,,,,,0,0,0,,,,,,0,,,0,,0,,,,,,,,,

4,PRODUCT1,BP1,BP,,F1,,,,,BP1,BP,,1,EA,,6,,0:00:00,,,,1,,1,2,0,,,,,,,,,,,0,0,0,,,,,,0,,,0,,0,,,,,,,,,

1,,,,,,,,,,,,,,,E1,BIN3,,0:00:00,,PACKMAT,,2,,2,3,0,,,,,,,,,,,0,0,0,,,,,,0,,,0,,0,,,,,,,,,

4,PRODUCT1,BP,BP,,F1,,,,,BP1,BP,,1,EA,,6,,0:00:00,,,,2,,2,4,0,,,,,,,,,,,0,0,0,,,,,,0,,,0,,0,,,,,,,,,

1,,,,,,,,,,,,,,,E1,BIN3,,0:00:00,,PACKMAT,,3,,3,5,0,,,,,,,,,,,0,0,0,,,,,,0,,,0,,0,,,,,,,,,

4,PRODUCT1,BP,BP,,F1,,,,,BP1,BP,,1,EA,,6,,0:00:00,,,,3,,3,6,0,,,,,,,,,,,0,0,0,,,,,,0,,,0,,0,,,,,,,,,

1,,,,,,,,,,,,,,,E1,BIN3,,0:00:00,,PACKMAT,,4,,4,7,0,,,,,,,,,,,0,0,0,,,,,,0,,,0,,0,,,,,,,,,

4,PRODUCT1,BP,BP,,F1,,,,,BP1,BP,,1,EA,,6,,0:00:00,,,,4,,4,8,0,,,,,,,,,,,0,0,0,,,,,,0,,,0,,0,,,,,,,,,

Thanks

Sasidhar Gupta

Source: https://community.sap.com/t5/supply-chain-management-blogs-by-members/initial-stock-upload-in-ewm/ba-p/13077635

    Manufacturing in SAP S/4HANA Cloud Public Edition 2402

     This blog post provides an overview of innovations in SAP S/4HANA Cloud Public Edition release 2402 for the line of business Manufacturing.

    Table of Contents

    Production Engineering

    • New SAP Fiori app Manage Production Resources and Tools
    • Mapping of Custom Fields in Tasklists to Work-Center Formula Parameters
    • Developer Extensibility: New RAP Business Object for Production Routing

    Production Planning

    • Demand Forecasting with SAP IBP and SAP S/4HANA Cloud Public Edition (▶️demo video)

    • Demand-Driven Replenishment
    • Capacity Scheduling Board
    • Evaluate Capacity
    • CDS Views for Production Planning
    • Objects Changed for Developer Extensibility in Material Requirements Planning (▶️demo video)
    • Schedule Handover of Purchase Requisitions

    Production Operations

    • Developer Extensibility: New RAP Business Object for Process Order
    • OData API Production Order - Update customer fields on order header
    • Kanban Control Cycle OData Operation - Retry Failed Container Status Change (▶️demo video)

    Quality Management

    • Navigation from Manage Inspection Lots to other native SAP Fiori apps
    • Enhancements to Record Inspection Results app
    • Integrating defects in quality notification
    • Objects released for developer extensibility

    More Information / Additional links

    Check out my video highlighting the following manufacturing release highlights:

    • Integration with SAP IBP for Demand
    • Drag and Drop in Capacity Scheduling Board
    • Extensibility in Production Operations

     

    Production Engineering

    New SAP Fiori app Manage Production Resources and Tools

    With the new SAP Fiori app Manage Production Resources and Tools, you can perform all operations related to creating PRT, changing PRT, and displaying PRT.

    Figure 1: New SAP Fiori app 'Manage Production Resources and Tools'Figure 1: New SAP Fiori app 'Manage Production Resources and Tools'

    Mapping of Custom Fields in Tasklists to Work-Center Formula Parameters

    With the new SSCUI Mapping Custom Tasklist Operation Fields to Work Center Formula Parameters you can map the custom fields created for the tasklist (Routing, Recipe) to the Formula Parameters in the work center. The values will be dynamically generated based on this custom field and it is used in the Operation details, Costing and Scheduling modules.

    Figure 2: 'Mange Your Solution' app - New configuration step 'Mapping Custom Tasklist Operation Fields to Work Center Formula Parameters'Figure 2: 'Mange Your Solution' app - New configuration step 'Mapping Custom Tasklist Operation Fields to Work Center Formula Parameters'

    Developer Extensibility: New RAP Business Object for Production Routing

    For SAP S/4HANA Cloud ABAP Environment, the business object interface Production Routing is released for developer extensibility. With this RAP (ABAP RESTful Application Programming Model) business object, you can build custom applications for creating, updating, and reading a production routing as a business object of ABAP RESTful application programming model in SAP S/4HANA Cloud ABAP Environment.

    Figure 3: Business object interface for Production RoutingFigure 3: Business object interface for Production Routing

     

    Production Planning

    Demand Forecasting with SAP IBP and SAP S/4HANA Cloud Public Edition

    Enable bidirectional integration for demand forecasting scenario with SAP S/4HANA Cloud and SAP Integrated Business Planning for Supply Chain using SAP Integration Suite:

    • Integration of product, location, customer master data and sales history data from SAP S/4HANA Cloud to SAP Integrated Business Planning for Supply Chain
    • Integration of final consensus forecast from SAP Integrated Business Planning for Supply Chain to SAP S/4HANA Cloud using SAP Integration Suite

    Demand-Driven Replenishment

    The new features include the following:

    • Exclude products which are not relevant for MRP based on Material Status as per Basic data or MRP1 view, Purchasing view of Material Master for classification.

    • Exclude or limit processing of phantom or bulk products in Demand-Driven Replenishment by excluding them in Buffer Management and Lead Time Classification in the following apps and application jobs:

      • Historical Buffer Performance

      • Mass Maintenance of Products (DD)

      • Buffer Positioning

      • Manage Buffer Levels

      • Replenishment Planning

      • Schedule Product Classification (DD)

      • Schedule Lead Time Classification of Products (DD)

      • Schedule Buffer Proposal Calculation

    Figure 4: Bulk Material & Phantom Assembly Filter AdaptionsFigure 4: Bulk Material & Phantom Assembly Filter Adaptions

    Capacity Scheduling Board

    With this feature, you can:

    • Reschedule operations on the Manage Operation page by dragging and dropping the operation on the chart within the same work center. You can only drag and drop to reschedule bottleneck operations.

    Figure 5: Drag & Drop in Capacity Scheduling Board (Manage Operation page)Figure 5: Drag & Drop in Capacity Scheduling Board (Manage Operation page)

    • The legend for orders are now changed to a blue palette. The Filtered and Unfiltered Operations in the legend are now moved to a scroll bar.

    Figure 6: Legend Color ChangeFigure 6: Legend Color Change

    Evaluate Capacity

    With this feature, you can navigate to the Capacity Scheduling Table app through the Schedule Production button provided in the Table View and the Chart and Table View in the Operations section.

    Figure 7: Evaluate Capacity link to Schedule Production

    CDS Views for Production Planning

    The CDS view MRP Plant Control Parameters was released for Production Planning.

    Objects Changed for Developer Extensibility in Material Requirements Planning

    With the objects released in Material Requirements Planning, you have a stable interface to access data from SAP S/4HANA Cloud when building custom applications or extensions with developer extensibility. You can integrate the released objects in your custom code or extend them at predefined extension points. Depending on your use case, different object types are provided (such as BAdIs, CDS views, business object interfaces). You find all the released objects in the ABAP Development Tools (ADT), when you're connected to SAP S/4HANA Cloud.

    Figure 8: Demo MRP apps: modernization and extensibilityFigure 8: Demo MRP apps: modernization and extensibility

    Schedule Handover of Purchase Requisitions

    With this new app you can schedule jobs to automatically hand over purchase requisitions in your area of responsibility to your purchasing department for further processing. The status Handover Pending of the selected purchase requisitions is set to Handover Completed. This application job app offers you an alternative to the manual step in the Hand Over Purchase Requisitions or Manage Material Coverage apps.

    Figure 9: Schedule Handover of Purchase Requisitions

     

    Production Operations

    Developer Extensibility: New RAP Business Object for Process Order

    For SAP S/4HANA Cloud ABAP Environment, the business object interface Process Order is released for developer extensibility. With this RAP (ABAP RESTful Application Programming Model) business object, you can build custom applications for processing, for example, creating, reading, updating, or deleting, the following entities of a process order:

    • Process order headers
    • Order items
    • Serial numbers
    • Order operations
    • Phases
    • Relationships
    • Order components

    Figure 10: Business object interface for Process OrderFigure 10: Business object interface for Process Order

    By the way: A year ago we launched the RAP Business Object for Production Order that enables you to modify a production order including production order header, components, and operations (see my 2302 blog post). This RAP business object enables us now to enhance the OData API for Production Order (Version 2). 

    OData API Production Order - Update customer fields on order header

    With the OData API Production Order (Version 2) (API_PRODUCTION_ORDER_2_SRV), you can create, read, and update production orders as well as set a wide range of statuses.

    The extensibility options for the Production Order entity (A_ProductionOrder_2) have been enhanced. You can now use your customer fields to also write data for the order header when you create or update your production orders.

    Figure 11: OData API Production Order allows now to update customer fields on order headerFigure 11: OData API Production Order allows now to update customer fields on order header

     

    Kanban Control Cycle OData Operation - Retry Failed Container Status Change

    The status change of a Kanban container in error state can now be retried via OData API. It was only possible via Kanban Correction app before.

    Pascal Rauprecht shows in the next video how you can automate the material replenishment from warehouse in case the kanban container runs into error status due to empty stock in the warehouse.

    Figure 12: Demo Kanban Control Cycle OData Operation - Retry Failed Container Status ChangeFigure 12: Demo Kanban Control Cycle OData Operation - Retry Failed Container Status Change

     

    Quality Management

    Navigation from Manage Inspection Lots to other native SAP Fiori apps

    With this feature, you can now navigate to apps in SAP Fiori instead of SAP GUI to record inspection results and make usage decisions from the Manage Inspection Lots app. It increases the usability of the manage inspection lot app through enhanced navigation. 

    Figure 13: Navigation from Manage Inspection Lots to other native SAP Fiori apps

     

    Enhancements to Record Inspection Results app

    You can use calculated characteristics in the Record Inspection Results app to calculate inspection results. This new feature will save time by letting the system automatically calculate inspection results according to a predefined formula.

    Figure 14: Calculated characteristics in the Record Inspection Results appFigure 14: Calculated characteristics in the Record Inspection Results app

     

    With this release you can also define conditional characteristics in an inspection plan. This ensures inspection of conditional characteristics depending on the results (after acceptance or after rejection) of the previous required characteristics within the same operation in the Record Inspection Results app. The conditional characteristics will improve the guidance for the quality technician recording inspection results.

    Figure 15: Conditional Characteristics in Record Inspection ResultsFigure 15: Conditional Characteristics in Record Inspection Results

     

    Integrating defects in quality notification

    In the SAP Fiori app "Manage Defects," you can leverage the new SSCUI to transfer defect categories to quality notification types. You can define combinations of notifications types and defect categories that are valid for the transfer of defects. The valid notification types can only be selected when you are transferring defects to the quality notification in the 'Manage Defects' app. This will greatly improve the flexibility for customers to transfer defects to different kinds of quality notifications.

    Figure 16: Integrating defects in quality notificationFigure 16: Integrating defects in quality notification

    Objects released for developer extensibility

    With this object released in Quality management, you have access to data from SAP S/4HANA Cloud when building custom applications or extensions with developer extensibility. You can integrate the released objects in your custom code or extend them at predefined extension points. Depending on your use case, different object types are provided (such as BAdIs, CDS views, business object interfaces).

    Figure 17: Objects released for developer extensibility in Quality Management

     

    More Information / Additional links

    Thanks for reading this blog post. Stay tuned!

    Follow us via @SAP and #S4HANA, or myself via LinkedIn and @GerhardWelker.

    Many thanks also to my co-author Markus Oertelt, who wrote chapter Production Planning and Leonie Peterka, who wrote chapter Quality Management.

    You will find a collection of SAP S/4HANA Cloud product centric blog posts from Markus and me here:

     

    Don’t hesitate to leave a comment and check out our new community page to ask your questions and engage with the experts. Follow the PSCC_Enablement tag to stay up to date with our latest blog posts.

    📽️ Watch Our Live Sessions

    In January 2024, we hosted a series of 19 compelling live sessions to highlight the exciting innovations shipped with the SAP S/4HANA Cloud Public Edition 2402 release. Missed the live sessions? No problem! Take advantage of the entire series or pick and choose the sessions most relevant to you on demand.

     

    🎙️ Inside SAP S/4HANA Cloud

    There is no customer success without project success and product success! Leverage the unique knowledge and expertise of SAP S/4HANA Cloud experts, partners, and customers, sharing their SAP S/4HANA Cloud implementation project best practices and lessons learned – anywhere, anytime. In this podcast, we give you all ingredients to get to the next level and make your SAP S/4HANA Cloud project a success. Subscribe now and benefit from the shared knowledge!

     

    💻openSAP Microlearnings for SAP S/4HANA Cloud

    Our openSAP microlearnings for SAP S/4HANA Cloud offer an exciting new learning opportunity. What began with a small batch of 20 videos, has now become a channel with more than 50 microlearnings that have generated over 20,000 views. Today, we cover multiple lines of business such as finance, manufacturing, and supply chain management, and key technology topics like Master Data Management, extensibility, SAP User Experience, and upgrade management. We are continuously adding new microlearnings to our channel, so make sure you check them out.

     

    🗣️ Your Voice Matters

    You want to learn more and actively engage with SAP subject matter experts on SAP S/4HANA Cloud topics? We have just the right place for you! Join our interactive community where we bring together customers, partners, and SAP experts with a clear mission: To engage with one another about best practices and product solutions. We invite you to explore the ‘one-stop shop’ as the central place for all resources, tools, content questions, answers and to connect with experts who will guide you through your journey to the intelligent, sustainable enterprise.

     

    🔎Find All of Our Assets

    SAP S/4HANA Cloud is the foundation of the intelligent, sustainable enterprise and is an innovative, robust, and scalable ERP. We at Cloud ERP Product Success and Cloud Co-Innovation offer a service as versatile as our product itself. Check out the numerous offerings our team has created for you below:

    Gerhard_Welker_0-1706795008089.png

     

    🎯Where to Find More Information:

     Source: https://community.sap.com/t5/enterprise-resource-planning-blogs-by-sap/manufacturing-in-sap-s-4hana-cloud-public-edition-2402/ba-p/13590769

    EWM warehouse connected to multiple Shipping Points locations

     

    Conceptualization:


    This blog is conceptualized on topic of '' How Shipping point determination happens in EWM when Warehouse is connected to multiple goods receiving and good shipping offices.

     

    Why we need this set up?


    There can be the cases when the EWM warehouse can be connected with multiple plants and all the stock of different plants is available in 1 Warehouse as each plants will be having its own ownership of stock. Once customer order is arrived, it would required to ship the delivery from different shipping points.

    In case of Inbound, goods coming from vendor can be received from multiple Goods receiving points for each plants.

     

    Mechanism of Shipping point determination in EWM


    During Inbound or outbound delivery creation in ERP, system picks the relevant shipping points based on settings of OVL2 and master data set up. The relevant shipping points assigned in ERP delivery documents is transferred to EWM system.

    --> But during creating delivery document in EWM, the EWM specific shipping point determination runs which doesn't take the outputs of the ERP shipping point determination into consideration. EWM shipping points determinations has its own separate logic.

    • EWM first reads the shipping points assigned  as Shipping office( SO) for outbound delivery and Goods receipt office as (RO) in Supply chain Unit, in case of single shipping point.


     



     

    --->The standard determination logic is in the class /SCWM/CL_EI_DLV_OFFICE_DET(Fallback class) which is called in Badi /SCWM/EX_DLV_OFFICE_DET.

     



     

    For determination of EWM specific shipping point, system check 2 values

    1. sc_party_role_ro(goods receipt point) for inbound delivery and expected goods receipt, 

    2. sc_party_role_so( shipping office) for outbound delivery.


     

     

    If warehouse is connected to multiple shipping points, you need to create SCU manually in EWM.


    Execute t code /SCMB/SCUMAIN. Use location type 1003 for shipping point and chose create. On the business attribute tab, use RO and SO.



     

    Now, it is required to create SCU hierarchy for the above Shipping point SCU in /SCMB/SCUHIERMAIN.

    Latter, you need to assign multiple goods receipt offices and shipping offices to a warehouse in the hierarachy of the supply chain unit .

     When multiple shipping points are used in EWM, it is required to use a Badi /SCWM/EX_DLV_OFFICE_DET



     

    There is fallback class /SCWM/CL_EI_DLV_OFFICE_DET which looks into the old logic of shipping point determination from Warehouse.

    But if you have activate the new logic,shipping point determination sent from ERP delivery document is transferred to EWM delivery documents,and this fallback class is ignored.

    To activate the new logic, create your own implementation of the BAdi
    /SCWM/EX_DLV_OFFICE_DET

     



     

    This badi calls the class /SCWM/CL_EI_DLV_OFFICE_DETER( new logic) which looks into the shipping points sent from ERP delivery documents (IBD, PDI, EGR) instead of old logic. If this badi is not activated, system looks into old fallback class.

     



     



     

    Hence, the topic ends here. Corrections and improvements required to make this blog more useful is welcome.

     

    Best regards

    Shailesh Mishra

    Source: https://community.sap.com/t5/supply-chain-management-blogs-by-members/ewm-warehouse-connected-to-multiple-shipping-points-locations/ba-p/13403475