Illustrating the Request from Logistics

Integrating a compliance-relevant product master with the compliance view is key to integrating product compliance processing with the value chain.

The initial step is to identify a product master that is compliance-relevant, automatically triggering a logistics request.

Some details in the Product Master provide essential information, such as to which countries/regions the product shall be sold or where it shall be produced. Also, changes to such information must be forwarded to the product stewardship specialist. Only then can the required compliance and market assessments be initiated, and compliance information can be provided upfront.

1. Edit the compliance-relevant product master by the Master Data Specialist - Product Master.
2. The system automatically creates requests from logistics.
3. Check request from logistics by Product Stewardship Specialist - Product Compliance.
4. Review and adapt the affected compliance view by the Product Stewardship Specialist - Product Compliance.
5. Process compliance assessments.

The following details of the product master are relevant for the automated creation of requests from logistics:

• Compliance Relevant - this must be set to 'Yes'; requests from logistics are only created for compliance-relevant products.
• Distribution Chains - distribution chains indicate that the product is sold to respective markets, which means countries/regions.
• Plants - plants with the maintained procurement type per plant indicate production.

Users of the Compliance Information for Products app, for example, internal sales representatives and marketing specialists, can manually initiate requests from logistics in case there is no valid compliance information available for a country/region identified in the map view or table view.

Manual requests from logistics can be initiated for Product Marketability - you can create requests:

• In sales view of product marketability for business process ‘Sell In’, or
• In the production view of product marketability for the business process ‘Produce In’.

Requesting a marketability assessment for a new country/region requires the product stewardship specialist to do the following:

1. Review and adjust assigned compliance purposes.
2. Process additional compliance assessments for solution areas.
3. Consolidate assessment results in the requested market assessment and business process.

Processing of product compliance checks is integrated with the supply chain. If the following checks detect missing compliance data, a request from logistics is created automatically.

Product Marketability - selling the product to a market, respectively a country/region, derived from the ship-to party, for which there is not yet a valid and released market assessment for the business process ‘Sell In’ in the solution area product marketability.

Special permission required - in product marketability, you have two situations where special permission may be required, and thus, a request from logistics can be created from a logistics document.

Dangerous Goods - shipping the product to a market, respectively a country/region, derived from the ship-to party, for which there is not yet a released dangerous goods assessment for at least one domestic mode of transport, besides at least one international mode.

Safety Data Sheets - in case there is no valid and released safety data sheet assessment in safety data sheet management for the country/region derived from the ship-to party, a request from logistics is created for the solution area safety data sheets.

Compliance checks on a logistics document automatically create a request from logistics when:

• The product is sold or delivered to the customer in a new market country/region, so a new market assessment is required.
• Compliance checks identify missing compliance data:
  • No released dangerous goods assessment exists for the country/region of the ship-to party.
  • The safety data sheet is unavailable for the country/region or the required languages.
• Marketability status for selling to a market is allowed with restriction, so individual permission is required for the business transaction.
• A customer compliance check is applicable but not yet available for the customer buying the affected product.

In these cases, the following details are provided with the request from logistics:

• The business process, the solution area, and the area (country/region) that are derived from the failed compliance check;
• Logistics document type (sales order, outbound delivery, or transportation order) and the document ID number;
• Requester - this means the user working on the logistics document;
• The affected product.

The following is an example of the processing of a request from logistics: the master data specialist - product master creates a new product with the following details:

• The product is compliance-relevant.
• There are distribution chains and plants maintained.

Because the product is relevant to compliance, a request from logistics is automatically created.

From the details, the following is derived:

• The existing distribution chains result in the proposed logistics role "Sold".
• The role of "Sold" is always combined with the logistics role of "Transported".
• Market countries/regions are derived from the countries/regions related to the sales organizations of the distribution chains.

The Requests from Logistics are automatically created for products, as compliance-relevant, and require further processing of requests by product compliance business roles.

With the assignment of the logistics role 'Transported' and the assignment of a compliance purpose, comprising dangerous goods compliance requirements, dangerous goods classification processing is initiated.

This applies to unpackaged products and raw materials according to business needs.

To complete the dangerous goods classification, you need to assign packaged products from the product master to the respective compliance views.

The Process Requests from Logistics app provides an overview of new logistics requests in the Unprocessed section.

Utilize the search to retrieve a specific request from logistics by product name, business process, reason for request, origin, or due date.

With the automatically created Request from Logistics, you get an insight into the compliance information required:

• Request Details - this section provides information related to the origin of the request:
  • The product in the product master for new products;
  • The logistics document, for example, a sales order;
  • The manual request that is created in the Compliance Information app.
• Compliance View:
  • For a new product in the product master, you can assign an existing compliance view or create a new one.
  • For products already assigned, you will find the compliance view for unpacked products in this section.
• Countries/Regions to Verify - originate from:
  • Distribution chains or plant views that are maintained in the product master;
  • Logistics document, for example, a sales order in case no market assessment is available;
  • Manual request.
• Compliance Purposes to Verify: In this section, you find the compliance purposes of an existing compliance view assigned.

If you create a new compliance view for unpackaged products, you can add compliance purposes.

In the Request Details, you get an overview comprising the following:

• The affected product is in the Product Master.
• Sales organizations - this originates from distribution chains maintained for the product.
• Plants - this originates from plant views maintained for the product.

In the request, you can create a new compliance view or assign an existing compliance view to the product in the product master:

• Create a compliance view for Packaged products: The new product is a packaged product for assignment to a new compliance view of unpackaged products.
• Assign compliance view to Unpackaged Product: The new product is unpackaged and is to be assigned to an existing compliance view for an unpackaged product.
• Create a compliance view for Unpackaged Product: The new product is unpackaged and will be assigned to the newly created compliance view for an unpackaged product.

You decided to create a new compliance view for the unpackaged product.

The logistics roles Sold and Transported are automatically proposed.

You can add logistics roles as required. For example, you need the logistics role produced.

The countries/regions to verify are derived from those countries/regions related to the following:

• Distribution chains;
• Plant views.

Maintained the product in the product master.

In the section, Compliance Purposes to Verify, you can add compliance purposes, which you identify as needed, according to the information you get from the request from logistics.

The default compliance purposes will be assigned automatically upon creating the compliance view.

This applies to raw materials and products.

With the action, Ready for Assessment, you finalize the logistics request.

You can immediately start working on compliance assessments with the action, Assess Now, or save the request for later processing.

You will find requests from logistics in the In Assessment section until all pending market assessments are completed with a compliance status for:

• Countries/Regions to verify;
• Related business processes.

Requests from Logistics integrate product compliance processing with the supply chain. They can be triggered automatically by system changes or manually by users.

The Process Requests from Logistics app provides a central location to review, process, and manage these requests.

Compliance checks during logistics transactions (like sales orders) automatically trigger requests if compliance data is missing or requires review.