[Audio] Before initiating an Internal Order request, it's crucial to have essential data elements in place to guarantee a seamless process and precise allocations. This includes identifying the brands the budget will be allocated to, defining the type of activity or budget category, ensuring relevant profit and cost centres are identified, determining the geographical focus of the IO, and specifying the GL code. Additionally, user details are required for ID creation. Once these pre-requisites are met, users can submit their IO request with detailed budgetary and activity information in BPRISM, generating a unique tracking identifier.. 

Scene 1

Step 1: Pre-Requisites Before an IO (Internal Order) request can be initiated, essential data elements must be in place to ensure a smooth process and accurate allocations. These include: Brands: Identify which brand(s) the budget will be allocated to. Activity/Budget Type: Define the type of activity or budget category (e.g., A&P, S&D) to align with financial planning. Profit & Cost Centres: Ensure relevant profit and cost centres are identified to allocate expenses accurately. Zones & States: Determine the geographical focus of the IO, necessary for tracking regional budget allocations. GL Code: GL codes master is used for categorizing financial transactions. User Details: Details of users list required for ID creation 
  Step 2: IO Request Submission Users to fill the IO request with detailed budgetary and activity information in BPRISM to initiate the process and receive a unique tracking identifier. Information to be Provided: Budget Type Definition: Specify the type of budget requested, aligning with organizational standards (e.g., A&P, S&D). Brand Selection: Define the brand for which the funds are intended. Budget Amount: Enter the requested budget amount. Activity Period: Outline the duration over which the budget will be used, including start and end dates. Supporting Approvals & Workings: Attach necessary approvals and detailed financial workings to justify the budget request. Zone & State Selection: Define the geographical regions where the budget will be utilized to aid regional financial tracking. Upon completing the above, the system generates a “Unique IO Request Number”, allowing easy tracking and reference throughout the process.

BPRISM IO Request & IO Creation Process Flow I/III

[Audio] As we proceed with the internal order creation in SAP, we begin by inputting essential data into BPRISM. This includes brand, budget type, IO amount, activity period, zone, state, supporting documentation, and approvals. We then verify the supporting documentation, validate the budget head, confirm the amount, and update the hierarchy. The system generates a unique IO request number, allowing us to track and reference the process easily. However, if there's any discrepancy, we start again from scratch.. 

Scene 2

BPRISM Process Flow Chart – IO Request & IO Creation

Input Data in BPRISM : Brand Budget Type IO Amount Activity Period Zone & State Supporting & Approvals

IO Creation & Validation Verification of Supporting Documentation Budget Head Validation Amount Confirmation

Stages within IO Creation  IO Number Generation GL Mapping, Activity & Amount Allocation Hierarchy Update

*Infomap will provide Portal access to the Users & Client

Upon completing the above, the system generates a Unique IO Request Number, allowing easy tracking and reference throughout the process.

Upon creation & updation of Internal Order (IO) in SAP, IO will be updated against the BPRISM Request ID. User can view the IO number through IO request ID under “Approved Internal Order” Tab in BPRISM.

IO creator will Upload the SAP IO number against BPRISM Request & Close the ticket.

IO Process - Copy (2)

Before initiating an Internal Order request, it's crucial to have essential data elements in place to guarantee a seamless process and precise allocations. This includes identifying the brands the budget will be allocated to, defining the type of activity or budget category, ensuring relevant profit and cost centres are identified, determining the geographical focus of the IO, and specifying the GL code. Additionally, user details are required for ID creation. Once these pre requisites are met, users can submit their IO request with detailed budgetary and activity information in BPRISM, generating a unique tracking identifier.

avatar

As we proceed with the internal order creation in S-A-P--, we begin by inputting essential data into BPRISM. This includes brand, budget type, IO amount, activity period, zone, state, supporting documentation, and approvals. We then verify the supporting documentation, validate the budget head, confirm the amount, and update the hierarchy. The system generates a unique IO request number, allowing us to track and reference the process easily. However, if there's any discrepancy, we start again from scratch.

IO Process - Copy (2)

Scene 1 (0s)

Scene 2 (1m 5s)