chanduk
Member
Hi all ,
Presently we are using standerd cost (07) method methods for all procured and manufacturing product.But client want to use weighted average (02) cost instead of standerd cost(07).
For the same followings steps we are going to follow but if is there any impact on product costing can we keep the Cost componants in(F30026) 07 cost method.
Steps.....
1)Utilising the R41052 batch application and some conversion actions you should be able to move over from '07' to '02' based costs smoothly. Please see below for suggested steps.
Requirements:
1. Write journal entries only where the '07' and '02' costs are different.
2. Create / retain current '02' costs and keep the current '07' costs.
3. Make the '02' cost the current sales/inventory cost method.
The R41052 Batch copies the cost from the cost method entered in processing option 1 to the cost method specified in the data selection. There are three versions, one for each of the inventory cost levels. Use a copy of the appropriate XJDE version that matches your cost regime.
Suggested steps:
1. Back up your F4105 to a temporary library.
2. In UDC table 40/CM, add a new, previously unused cost method. (for example: '21')
3. Run the R41052 Future Cost Update with processing option #1set to '21'and with the cost method in the data selection set to 07. You may wish to use additional data selection to limit the records that this job runs over, based on your business requirements. This will create cost method '21' F4105 records
that have the same cost as the original '07' costs for all selected items. Because cost method '21' is not the sales/inventory cost method, no journal entries are required. The purpose of this step is to save the '07' costs for later use.
4. Run the R41052 Future Cost Update with processing option #1 set to '07' and with the cost method in the data selection set to '02'. This will move the '02' costs into the 07 records and write necessary journal entries. This uses DMAAIs 4172 and 4174with default document type of WD.
5. Using SQL, selecting the same set of items as you used in the P4105 (step 4 above), clear the F4105 COCSIN flag (costing selection - inventory) field in the cost method '07' records and populate the COCSIN field with an "I" for the '02' records. This changes the sales/inventory cost method from '07' to '02'. Because the '02' and '07' costs are identical at this point, no journal entries are required.
6. Run the R41052 Future Cost Update with processing option #1 set to '07' and the cost method in the data selection to '21'. This moves the '21' cost into the '07' record, restoring the original '07' costs. Because the '07' record is no longer the sales/inventory cost method, no journal entries are required.
7. Back up the F4105 to a second temporary library.
8. Purge the cost method '21' records from the F4105.
In performing this you will retain original cost references, create new average cost values and have your system setup to process. When next trasnaction come in on the system the weighted average algorithm will adjust the current values away from the '07' benchmark.
Please let me know if you have any questions based on the back of these suggestions. If not and there is a delay in enacting then the best thing would be to close case off pending you actually attempting a conversion test and open a new case should you run into problems.
Presently we are using standerd cost (07) method methods for all procured and manufacturing product.But client want to use weighted average (02) cost instead of standerd cost(07).
For the same followings steps we are going to follow but if is there any impact on product costing can we keep the Cost componants in(F30026) 07 cost method.
Steps.....
1)Utilising the R41052 batch application and some conversion actions you should be able to move over from '07' to '02' based costs smoothly. Please see below for suggested steps.
Requirements:
1. Write journal entries only where the '07' and '02' costs are different.
2. Create / retain current '02' costs and keep the current '07' costs.
3. Make the '02' cost the current sales/inventory cost method.
The R41052 Batch copies the cost from the cost method entered in processing option 1 to the cost method specified in the data selection. There are three versions, one for each of the inventory cost levels. Use a copy of the appropriate XJDE version that matches your cost regime.
Suggested steps:
1. Back up your F4105 to a temporary library.
2. In UDC table 40/CM, add a new, previously unused cost method. (for example: '21')
3. Run the R41052 Future Cost Update with processing option #1set to '21'and with the cost method in the data selection set to 07. You may wish to use additional data selection to limit the records that this job runs over, based on your business requirements. This will create cost method '21' F4105 records
that have the same cost as the original '07' costs for all selected items. Because cost method '21' is not the sales/inventory cost method, no journal entries are required. The purpose of this step is to save the '07' costs for later use.
4. Run the R41052 Future Cost Update with processing option #1 set to '07' and with the cost method in the data selection set to '02'. This will move the '02' costs into the 07 records and write necessary journal entries. This uses DMAAIs 4172 and 4174with default document type of WD.
5. Using SQL, selecting the same set of items as you used in the P4105 (step 4 above), clear the F4105 COCSIN flag (costing selection - inventory) field in the cost method '07' records and populate the COCSIN field with an "I" for the '02' records. This changes the sales/inventory cost method from '07' to '02'. Because the '02' and '07' costs are identical at this point, no journal entries are required.
6. Run the R41052 Future Cost Update with processing option #1 set to '07' and the cost method in the data selection to '21'. This moves the '21' cost into the '07' record, restoring the original '07' costs. Because the '07' record is no longer the sales/inventory cost method, no journal entries are required.
7. Back up the F4105 to a second temporary library.
8. Purge the cost method '21' records from the F4105.
In performing this you will retain original cost references, create new average cost values and have your system setup to process. When next trasnaction come in on the system the weighted average algorithm will adjust the current values away from the '07' benchmark.
Please let me know if you have any questions based on the back of these suggestions. If not and there is a delay in enacting then the best thing would be to close case off pending you actually attempting a conversion test and open a new case should you run into problems.
