Pricing procedure related queries and interview questions

41.Question: How pricing procedure will trigger in PO?

Answer: 

pricing procedure will trigger in PO with respect to schema determination.

We have a standard schema determination and as per our company requirements, we may have our own conditions and for that we need to create a new schema determination.

We have schema group for vendor and schema group for purchase organization.

Assign schema group (Vendor) and schema group (Purchase organization) with your purchase organization and assign vendor schema group to vendor master.

Now as per the vendor in PO, the schema determination will trigger in PO with conditions.

42.Question: What pricing procedure contains and how it works?

       Answer:

 pricing procedure contains:

1.      Condition fields

2.      Condition tables

3.      Access sequence

4.      Condition type

5.      Calculation schema

When we create PO with vendor and purchase organization then as per the configuration made system will choose the calculation schema based on vendor and purchase organization.

Now all the condition maintained in calculation schema will be seen in PO with the help of schema group.

Now, as per the fields we maintained in PO, like material/vendor/plant system will check the condition fields and triggers the price.

Here condition fields are maintained in condition tables and condition table is linked to access sequence and finally access sequence is maintained in condition type.

Every condition type is linked to calculation schema.

              

43.Question: What is the use of requirement and accrual key in pricing procedure?

Answer: Requirement:

Requirement filed will be presented in calculation schema, where if we maintain required check then those conditions will appear in the PO conditions and if there is no value then we can maintain as statistical check.

Accrual Key:

This we will use as per the company requirements, where If we have own conditions for freight then we can have our own accrual key FRL.

We need to define new accrual key if required and maintain GL account in that field.

Ticket: - Account key with accrual Key

44.Question: What is IDOC and explain configuration:

Answer:

IDOC is an intermediate document where data flows from two systems inflow and outflow.

We can call as inbound and outbound, if we are transferring data to vendor like PO copy then it called as outbound and vendor is sending order confirmation to company then its inbound.

We used EDI IDOC, in which we have done setup for output condition record the data when we save PO then it flows directly to vendor through IDOC.

We have segment and all fields are mapped in the segments and once we select the receiving vendor then we need to maintain the vendor number with processing type and maintain outbound options.

Maintain partner role and message type and enter- continue with mentioning port number with basic type and extension and, we need to maintain application, message type and process code.

Lastly, we will maintain the agent id- where when idoc fails it will send the notification to user.