Business Blue Print regarding

[Former Member]

Hi Guru's, Can any body send me a document on BBP, because it is not found in the previous thread lists.

Thanx in advance,

My mail id is Thakur_tulja@yahoo.co.in.

[Former Member]

Murali, you are right , Blue prints are always company specific

But it would be helpful for new persons to have an idea about it and to know what things needs to be covered and in waht fashion.

Therefore I would appreciate if someone can send it at sandeepmarwha@rediffmail.com too

Thx in advance

Sandeep

[hnmuralidhara]

Hi,

BBP for Invoice Verification goes as below;

<b>Scope & Brief description</b>

It is in Logistics Invoice Verification that Incoming Invoices are verified in terms of their content, prices and arithmetic. When the invoice is posted, the invoice data is saved in the system. The system updates the data saved in the invoice documents in Materials Management and Financial Accounting.

The Invoice Verification will be carried out against

a) Purchase Order/Scheduling Agreement

b) Delivery

c) Bill of Lading

d) Service Entry Sheet

e) Vendor ...etc.

Evaluated Receipt Settlement (ERS) allows you to settle goods receipts without receiving an invoice. Based on the order price specified in the purchase order and the quantity entered on the goods receipt, the system can determine the correct invoice amount. The system also obtains tax information and terms of payment from the purchase order. This information allows the system to settle without having to process a vendor invoice.

The Evaluated Receipt Settlement (ERS) function has the following advantages:

a) Reduction of steps involved in the purchasing/receipt/invoice/payment cycle

b) Reduction of clerical errors

c) Elimination of price and quantity variances in the Invoice Verification process

<b>Expectations / Requirements</b>

Logistics Invoice Verification should be carried out with reference to the Purchase Order, against the Goods Received in the Stores.

Various Logistics Invoice Verification scenarios are explained in detail below:

(a) Invoice : Vendor will issue invoice against for the Goods Received against the Purchase Order. The system will propose the value on the basis of Goods Received and the rates maintained in the conditions. The Logistics invoice verification will be carried out in will be posted. Any unplanned cost will be captured in ILV and will be posted.

(b) Credit Memo: In case the LIV is already posted in the system and because of some reasons the material is rejected and is to be returned to the Vendor. Then in that case Vendor is to be debited to the value of material to be returned to the Vendor. The posting will be done through Credit Memo option available in the system.

(c) Subsequent Debit: The Vendor has already given the invoice for all the goods received. Subsequently, freight costs are to be taken into account, then the additional Freight Costs will be Captured by using the option Subsequent Debit, the value will be entered in the system and the quantity remains the same. The Value will get uniformly gets loaded on the Material.

(d) Subsequent Credit: You have already posted a credit memo in the system for damages to the goods supplied; now you want to further deduct an amount on account of Damages then Subsequent credit can be used for such process.

Invoice can be cancelled in the SAP system. The system will post another entry with reversed accounting entries.

<b>Explanation of Functions and Events</b>

Here you have to explain business Mapping for various types

<b>Business Model</b>

Here you have to incorporate your process flow-chart

<b>Changes to existing Processes and its Implications</b>

Here you have to explain legacy and SAP process and its implication. For example, Currently all Logistics Invoice Verification are posted by account Department in XYZ Compnay.

<b>Description of Improvements</b>

The Logistic Invoice Verification will be carried out against the Goods Receipt only.

<b>Data Migration Considerations</b>

If any open data to be uploaded at the time of Go-live. (Preferably this should be NONE for this process)

<b>Interface Considerations</b>

Any third party interface and its implication

<b>Authorization and User Roles</b>

Logistics Invoice Verification authorization to be with the Users in Account Department.

<b>Reports</b>

Client report requirements

Bye,

Muralidhara

[hnmuralidhara]

Hi Tulji,

BBP document varies from Client to Client.

This document contains, legacy business process, Scope and brief description, expectations, business model, changes and its implication, description of improvements, Gaps and possible approaches to bridge the gas, System configuration consideration, data migration, interface and Authorization and user roles

Bye,

Muralidhara