RHB:Implementations in Q4.2023

This innovation project is using our brand new HR Hub, P2P Hub and FI Hub. For RhB we are developing the new Pool Order Management functionality, consisting of the brand new purchase order pool manager app and extensions to the approval agent.

HR Hub

This is the first customre using the new HR Hub.

Pool ordering process

• Purchase order pool management - all purchase orders made by staff members need to be put into a pool order (standard functionality of purchase order pools)
• Non-standard functionality upon release
  1. A pool-order-release-job shall be created
  2. This job immediately creates a info-purchase-order (standard functionality done by approval agent)
  3. This pool-order-release-job shall be sent to SAP for 3rd party system approval (P2P Plugin to be developed)
  4. Once SAP has returned an approval for the info (through another P2P-Plugin) the plugin (1) marks the pool-order-release-job ias approved and (2) provides the partial approval mark to all purchase orders.
  5. With this done the "small" purchase orders in the pool have received their last partial approval and the approval agent marks them as fully approved. (Standard functionality by approval agent)
  6. As the order is placed, the network connector will now:
     1. transmit the "small" pos to the b-op network partners.
     2. create expected deliveries/shipments for non b-op network partners.

Mathias has found out, that purchase orders created through the ui are not subject to approval agent functionality but are automatically approved. This is technical debt as process flow governance shall NEVER be part of UI components. This flaw must be resolved in order to make the processes work as expected.

FI-Hub extensions

We have defined 5 cases of business processes

Pool orders ("Gesammelte Jahresbestellung")

Triggering process - see above. When goods as of an internal order targeting a staff member have arrived, the arrival is confirmed by de-minimis confirmation deamon or by staff members through task manager.

Once this has happened, the FI-Hub core captures an event of type "personal goods arrival confirmation of orders part of a pool order of a specific pool order UID". This shall trigger a RhB specific plugin, performing these actions:

• Items shall be booked against the inventory account and immediately
• booked out of the inventory account against the staff cost center of the user.

Lagerbestellung durch MW ("Lagerbestellung durch MW")

Triggering process - as personal ordering, only that there is another pool order UID, which catches orders which are triggered by a direct purchase order (no internal order) targetting a stock. Goods arrive through regular warehouse intake.

Once this has happened, the FI-Hub core captures an event of type"direct warehouse order goods arrival confirmation of orders part of a pool order of a specific pool order UID". This shall trigger a RhB specific plugin, performing these actions:

• items shall be booked against the inventory account

Handout of goods to costcenter or staff member from local stock ("Material-Entnahme von Lager RhB")

Items handed out from local stock are booked from the inventory account to the staff cost center. This is captured as a standard event of FI-plugin and sent to a FI-Plugin made for RhB.

Value change due to inventory job ("Lagerwertänderung (Sachkontoabgleich)")

When item value changed due to an inventory job, this is captured as a standard event of FI-plugin and sent to a FI-Plugin made for RhB.

Individual staff member order ("Individuelle Mitarbeiterbestellung bei Lieferant (zukünftiges Szenario)")

We need to establish another pool order type, which catches the personal individual staff orders. Plus we need another pool option "Immediately create pool-release job". This will release orders each in their own pool release job. The rest of the procedure will be the same as always.