Below is the narrative of the "Perform billing" portion of the B/AR/CR process.Narrative Description
When the OE/S process produces a sales order, it notifies the B/AR/CR process to that effect.This is the flow "Sales order notification." When triggered by the data flow, "Shipping's billing notification" (i.e., the shipping notice), process 1.1 validates the sale by comparing the details on the sales order
notification to those shown on shipping's billing notification.If discrepancies are noted, the request is rejected, i.e.a reject stub.Rejected requests are later processed through a separate exception routine.If the data flows match, process 1.1 sends a validated shipping notification to process 1.2.Process 1.2 then performs the following actions:
-Obtains from the customer master data containing certain standing data which is needed to produce the invoice.-Creates the invoice and sends it to the customer.-Updates the accounts receivable master data.-Adds an invoice to the sales event data (i.e., the sales journal).-Notifies the general ledger process that a sale has occurred (GL invoice update).Required:
From the DFD in TB Figure 11.1 and the narrative description above, explode bubble 1.0 into a lower-level diagram showing the details of that process.

Question

Quizplus · Accepted Answer

The Answer of Below is the narrative of the "Perform billing" portion of the B/AR/CR process.Narrative Description
When the OE/S process produces a sales order, it notifies the B/AR/CR process to that effect.This is the flow "Sales order notification." When triggered by the data flow, "Shipping's billing notification" (i.e., the shipping notice), process 1.1 validates the sale by comparing the details on the sales order
notification to those shown on shipping's billing notification.If discrepancies are noted, the request is rejected, i.e.a reject stub.Rejected requests are later processed through a separate exception routine.If the data flows match, process 1.1 sends a validated shipping notification to process 1.2.Process 1.2 then performs the following actions:
-Obtains from the customer master data containing certain standing data which is needed to produce the invoice.-Creates the invoice and sends it to the customer.-Updates the accounts receivable master data.-Adds an invoice to the sales event data (i.e., the sales journal).-Notifies the general ledger process that a sale has occurred (GL invoice update).Required:
From the DFD in TB Figure 11.1 and the narrative description above, explode bubble 1.0 into a lower-level diagram showing the details of that process.

Below Is the Narrative of the "Perform Billing" Portion of the B/AR/CR