reqt field

[Former Member]

Hello sap gurus,

1. What is the importance of requirment field in access sequence? Plz explain with an example.

2. What is cut over strategy?

[Lakshmipathi]

Dear Sabina

<b>1) Requirement Field</b>

This will decide how your output would be. For example, in some companies, at company code level, they would be having one currency but to do global business, they have to maintain multiple currencies.

In sales, in the case of exports, this requirement would be used to calculate customs dues at the currency used at Company Code level.

<b>2) Cutover Strategy</b>

This is nothing but you need to decide for cutting over the activities from the legacy system to SAP. This will differ from company to company.

Thanks

G. Lakshmipathi

[Former Member]

Reqirement field:

It minimises system work, if the condition type is satisfied, the reqirement specified in pricing procedure then only it will be determined in sales order.

cut over activity:

Make ready ness of production system

[Former Member]

<b>Requirement is nothing but PRE CONDITION</b>

If that condition satisfied that access will be checked

if not satisfied the access will not be considered.

Example:

Requirement 3 - Foreign currency

This requirement is met if the document currency and customer currency will be different.

It’s assigned in PR00 for condition table 6. This access is considered only when the currency differs as per requirement.

[Former Member]

I totally agree with kaustubha. its the perfect answer....

Regards,

Mohsin

[Former Member]

Hi ,

The requirement is nothing but the Routine ( Which we can see in Tcode VOFM )

This is certain minimal eligibility which should be meet to execute the access sequence.

Foe cut over stategy

What is cut over strategy?

Cutover strategy depends upon how the organizations design their data load strategies. Normally, you decide the sequence of Data loads for Configuration settings, Master data, Transaction data which follows whom and then you make a copy of the system as a Production system a day before and after checking the successful data loads, you go-live 100% or partial again depending upon organizational setup and policies.

Cutover planning is highly site specific. There's no thumb rule. The stock data as on the date of going live should be correctly entered. But stock being a highly dynamic quantity, the strategy for loading should be crystal clear. Then you have to load all the back dated transaction on the stock. Some stock comes into your plant/storage location as return and some stock is actually delivered to your customer through sales orders of various kinds.