request no

[Former Member]

1. What is the purpose of the request number which is generated when u save a customisation??

2. can u brief about Backward scheduling and forward scheduling?

[Former Member]

Hi Sabina,

1. What is the purpose of the request number which is generated when u save a customisation??

A:Request numebr is used when we transport config or customised data from one system to other system.There are 2 types of request one is workbench request which means development done by Abap coding. and the other one is customisation reqest which means configuration data.

2. can u brief about Backward scheduling and forward scheduling?

A:Backward scheduling is the calculation of deadline dates: the arrival time at the customer site is calculated as the earliest possible goods receipt time at the customers unloading point on the requested delivery date. All four of the delivery and transportation scheduling lead times are subtracted from the customer’s requested delivery date to determine if this date can be met.

The transit time, loading time, and pick/pack time are subtracted from the customer’s requested delivery date to calculate the required material availability date.

The system calculates backward scheduling as follows:

Requested delivery date minus transit time = Goods issue date

Goods issue date minus loading time = Loading date

Loading date minus transportation lead time = Transportation scheduling date

Loading date minus pick/pack time = Material availability date

By default, the system will calculate delivery dates the closest day, taking into consideration the working days of the shipping point and a rounding profile. In this case the system assumes a 24 hour work day and lead times can be entered in days up to 2 decimal points. This is referred to as daily scheduling.

Forward scheduling is also done if no product is available on the material availability date calculated by backward scheduling. The system does an availability check to determine the first possible date when product will be available. This new material availability date forms the starting point for scheduling the remaining activities. The loading time, pick/pack time, transit time, and transportation lead time are added to the new material availability date to calculate the confirmed delivery date.

Hope above answer clarify your query.

Reward points if it useful.

Regards,

Chandra

[Former Member]

Hi,

1. As you know in the realtime you will not do any configuration changes directly into production system, because the possibility of errors. If any config error happens in the production system, it may affect the business. So the config changes will be done in the development system, then it will be moved to test system through a request. This request number contains the changes. This will gie more control for the administrator and there by minimize the risk. After testing it it will be moved to the production system.

Backward scheduling : From the customer's requested delivery date from backwards (pick/pack/load/tp scheduling)

Forward Scheduling: From the Material availability date to froward (pick/pack/load/ tp schedule time...etc..)

Prase

[Former Member]

Dear Sabina,

The issues u have raised is completely 2 seperate topic in itself.

u r 1st query is regarding the Transport Request (TR)

To know about TR u should know the concept of System Landscap in SAP ( either 2 - 3 tier architechture)

1. Devlopment server

2. Quality server

3. Production server

In brief abut TR is, any changes made in either of these server will not affect auomatically in the other, to see the same changes made in another server/client TR will come into picture, where in when ever u change / customise in DEV it will ask for TR No. with this No. and through the transportation process ONLY u can see the changes in other server/client without doing any changes in other server/client (otherwise which is not a right practice to change directly in QLTY/ PRD Server)

As 95% configration is Client Dependent & 5% is Client Independent.

u can check the TC: se09 where in u have workbench & customising request radio button, select both and enter u will find n no. of TR nos. in Workbench & customising request.

Workbench is where in all the TR is ABAP related changes where as Customising is self explantory, its the request No. created for the customization we do in IMG.

Hope this information is sufficient, for further clarification revert back n correct me for any mistakes I have mentioned.

SECONDLY, Regarding the Backward / Forward Scheduling

Backward Scheduling is where in requested Delivery date is ahead of the Material Availbilty Date & Forward scheduling is if material is not available at particular requested date then request delivery date will be after the material available date.

With regards,

Vijayashree

[Former Member]

hi,

chnages that are made during customisation are stored into entities called 'trsport req'. wen the testing is ok and it is decided to move these chnages to other servers than its the transport req that are moved. while creating the req. care must be taken in naming- it shud identify the purpose, chnages and may the consultant who created the req. similar/related chnages can be put in the same req. others can have a diff one.

forward scheduling- from the present date to a date in future- the system cheks for the date in future wen the mats will be available.

bakwrd- the system begins from a future date bakwrds and finds out wen the goods will be availabe.

saurabh