Triage Guide

ZSD_HUB4D to view errors

The AHQ cockpit gives the user a snapshot of successful transactions and those that are in error. By
default the transaction is set to show open transactions only i.e. those in error.
The Company code needs to be entered NL02 for ENA,
It is advisable that a date/date range is also entered so that the report runs effectively.

Once the selections are complete, execute the report

The errored transactions are listed as per the example below. The exception status are clearly
identifiable by red (error) green (complete) or void (clear).

The scenario column gives a brief outline of what the transaction relates to with the source and
destination in both JDE and SAP codes. It is also possible to see the various reference numbers, i.e.
local PO numbers and delivery references.

To look at the transaction in more detail, double click on the line.

Here the user can see the JDE from plant and the destination plant along with the SAP mappings.
The top right shows the transaction number with a link to the actual Idoc message.
The organisation data is displayed on the left hand-side of the screen with the relevant virtual plant.
At the bottom the materials and quantities are listed.

The errors are displayed at the relevant points in the process

In the example above there is an error at the purchase order create stage, and therefore also the
sales order stage.
To see the detial of the error click on the scroll

The system will show the error in the following format, in this case a material has been ordered in
the IMEX which does not exist in SAP,

ZSD_HUB4D General view

Users can look at the successful transactions as well as those in error by selecting the All
transactions radio button, again, reccommended to specify a date/date range.

Every AHQ transaction will be shown for the dates specified. To view in detail double click on the
line.

In contrast to the first example, it is possible here to see the AHQ transactions which have been
created for the inter-company buy-sell process. Each of these can be looked at separately by
double-clicking into the document.
Looking at the below PO for example, the vendor, plant, materials and quantities have all populated
as per the transaction details.
The PO history tab at item level shows the user the subsequent goods receipt and invoice document.
These in turn can also be drilled into.

For the inter-company buy/sell purchase order to create successfully a valid source list must be in
place at material/plant level. This must contain the vendor and the relevant purchasing organisation
to ensure the system knows where the stock is being supplied from for a certain validity period.
These can be displayed through ME0M

Back to the buy/sell transactions the Sales order can also be displayed, drilling into each material
will show the selling price.

And also the user can look at the delivery and the status (C = completely processed).

External Manufacturer (also known as Copackers)

The external manufacturer process can be identified in the ZSD_HUB4D grid by scenario including
Ext.
A similar set of data is displayed at transactional level; virtual plant, purchasing group, To
destination.
Note that the external supplier has a six digit code, these are created and maintained on MDM.

The above transaction shows a receipt against the external manufacturer purchase order, the link
symbol links this transcation back to the original PO create

Once clicked, the system will take the user through to the PO create transaction.

As above, the purchase order requires a source list, in this scenario the souce list must include a
reference to a contract. ALL external manufacture purchase orders will be created with reference to
a contract. This contract must also include the FIX flag as highlighted below.

The contract which has been created and referenced must be in a released status, PO creation will
fail if the contract is blocked and/or it is not referenced on the source list with a fix flag.