Tickets and Details

8/2/2019 Tickets and Details

1/25

Ticket no:1851958

Description: Please update today table ZCFX_MRP_DISMM with P1 for plant CE01.

This setting has to be removed from table tomorrow.

Steps: T code: ZCFX_MRP_DISMM

Click Maintain

Click New entries , Enter the Plant and MRP type and Click SAVE , Click Back.


2/25

Ticket NO: 1831143

Description: L208072 stock is on ASB with Batch02 in Plant LX09 Where no batch management is

maintained for the particular material.

Reason: Check the material master whether the material has a Split Valuation, Valuation category.

Once the valuation Category is assigned the Field Batches (XCHAR) is populated.


3/25

While posting goods MB1C or MIGO the system will ask for the valuation type as mandatory.

If we enter the Valuation type the stock will be updated in the same as per the first slide. It Consider

the valuation type as batch.

To delete the valuation type We have to do following steps:

The existing stock should be made nil.

The work in process documents should be closed.

The previous period stock to be make zero.

The part no. is MRP relevant.

WIP Production orders to be closed.

The PR, PO & invoicing WIP documents to be closed.

All the TR & TOs to be closed and Bin stock to be made zero.Once all the above steps done successfully, then only it is possible to change the valuation

type.


4/25

Ticket NO: 1887207

Description:Change distribution list LX01_PPX52

TCode: SBWP

Click DistributionLists Button.

Select Shared Distribution Lists in the TYPE field and distribution name give in the ticket

like LX01_PPX52 the below screen appears,

Click CHANGE Button and delete the required names and ADD in the same way.

Ticket NO: 1914439


5/25

Description: Update of ZCMRP for John Deere Iberica.Purchasing organization A000,Plant

CE01

Tcode : ZCMRP

Select MRP Controller Radio Button

Enter Purchase Organization & Plant.

Click Execute.

Select the Purchase organization as in the ticket and then click Change button .The Below screen

appears.


6/25

Enter the USER ID as in the ticket and click SAVE.

SAME AS FOR THE MRP CONTROLLER CHANGE ALSO.

Ticket No: 1926470Description: Work the resport: ZINCON_REPROC with the components.


7/25

Tcode : ZC_conf_rep need to be checked for any Errors

Tcode : SM37 Batch Job reference *ZINCON* with nearest date

Details of job: ZINCON_REPROC(ZCCED_ZINCON_REPROC) Report is as attached below

The component has a RESB record with a given qty and no AFFW record.

All these cases are under the headline Reprocessing records with RESB-quantity neq 0 :

inside the report:

In this case 126 PC must be available on the storage location D160.

If we look into the stock details of the same component: DE19746


8/25

Before advising the user for the manual posting , check for if any manual

posting is already done for same material with same qty in MB51 or

MB03 .ifits done directly proceed to the last step ie.. Mail to Tier 3 to

delete the ZINCON_REPROC.

To post the component posting you must execute the MFBF transaction. Entry screen of the

MFBF:


9/25

In the MFBF you must first select the option component posting.

The option No BOM explosion..: you can keep activated.

Then you can copy the assembly material number out of the report with the plant:

Then you can click on the button Process component list to enter the component:

In the next screen (component list) you can copy the

Component material number (DE19746) out of the report with the qty (126)and storage

location: (D160)


10/25

.

Finally you can post the goods issue by clicking on the SAVE-button

With this posting the corresponding inconsistency is not deleted. For the deletion the report

ZINCON_REPROC must be executed with the DELETION-UPDATE-Flag, the plant and theconcerning component (MATERIAL):

The execution of the report ZINCON_REPROC with the DELETION-UPDATE-Flag can only be

done by the PP functional team(Mial need to be sent to TIER 3) .So if you have made some MFBF-component-postings please inform the PP functional

team and provide a list with all the posted components.

If a component occurs multiple in the report you must take that for all inconsistencies of the

component postings are done before you execute the report ZINCON_REPORC with the

DELETION-UPDATE-Flag for the component.

Ticket No: 1951325

Description: While creating the Production Order out of planned order of material BL15124

the below Error occur,


11/25

This is because in the planned order in the component overview we can observe that the

components or assembly are taking the produciton storage location as in the production

version fo the finished product.

first thing to notice whether the Finished product and assembly or components are assigned

to the same storage location.

The production version Issue storage location and receiving storage location.

Then check the MRP Group of the for which the material is assigned. TCODE: OPPR


12/25

As per this Strategy the production storage location is copied for finished product and for all the

assembly or components in the planned order.

While converting this planned order in to Production order the above error occurs Storage location

could not be adopted for the material.

Solution is to assign the components to the concern storage location to which the finished product is

assigned.

Note: The above error was occurred while creating if the production order is saved the all Error Logs

are deleted.

Ticket No: 1964023

Description: Storage locations not shown in planned order.

First thing to notice is Material master MRP4 View Selection Method field it suppose to be 2

or 3.

The production version issue storage location and receiving storage location.MRP Group Strategy in the Tcode: OPPR.


13/25

Solution change the Selection method in the MRP 4 view and run the MRP the Planned

order is created with storage location for the finished product and components.

Ticket No: 1971879

Description:ZCCSR_ALR: Entries of critical shortages list is different depending on the how

the list is printed.

When the list is printed overnight with the print job the entry "Last Receipt" is not shown.

Through the Batch Job ZCFXR_PPX21B_BANDABLAUF_REPO.

When the list is printed manually in the background, the entry "Last Receipt" is shown.

Through the Tcode ZCCSR_ALR.

In both the cases the Input parameters are selected form the Variant that assigned like

ZX01_400.

The Last receipt will be update in the report if the Check box of the field "LAST INCOMING

STOCK MOVEMENT WITH DEST. STORAGE TYPE" is marked in the Output selection TAB.

In this ticket the Variant that is assigned to the Batch is ZX01_400 which can be Checked in

the Table: TBTCP in which the Field is not mentioned . So the Batch is not Updated the Last

receipt Qty in the Report.

Solution is to modify the Variant with Required input parameters.


14/25

Ticket No: 1952198(Attach the screen shot)

Description:please check MD04 for material L169031LX3, mrp area LX01, plant LX01. you'll

see all requirements on a weekly basis: Feb 09th, Feb 16th, Feb 23rd, Mar 01st, Mar 08th,

etc. these requirements come from mrp area LX01_METOK. Here you'll find the

requirements on a daily basis, but the reservations are aggregated to a weekly basis.

Why???There is a very similar material that does not show this aggregation: L169032LX3.

First thing to notice is in MD04 just check the Weekly aggregated procurement proposal has

got Firming Indicator ( * ) .If it confirmed.

Go to the TCODE ZSE16N and enter the table name RESB and check the STATUS OF THE

RESERVATION (M-Manually and B - Automatically).As checked the Reservation for the

material L169032LX3 was posted manually in weekly basis. This can be checked in Table:

RESB in Status field shows M = reservation item was entered manually.

Whereas in the another material (L169032LX3) the Status field shows B = reservation item

was entered automatically

Field name = RSSTA & Description = STATUS of Reservation

Solution is deleting reservations...And Re Run the MRP for the Particular material.


15/25

Ticket: 1952198 (Screen Shots need to be attached)

Description:please check the MD04 for Material LG102510 unit LX01. there you can see 4

tractor orders with dates in the past (feb 07th, feb 15th). I checked the four production

orders with transaction COOIS and found out that 3 orders have completed the operation

0085 (to this operation LG102510 is assigned). These are the production

orders:8000304731, 8000304747, 8000308177 But when the operation 0085 is completed

for these orders, why is there no movement 261 in MB51 and why is there still the

requirement in MD04???

First thing to notice, In the Production order, in the operation overview check to which

operation, the Material LG102510 is assigned and checks its Control key.

Check the status of the operationwe noticed that the particular operation is confirmed

(CONF_MILE).

Next to check is Material document No MB51 .To check whether there any GI to the

particular order with movement type 261 if it is not found

Then check for COGI Error. We observed the Error in the COGI (Post processing Errors).

Note: Whenever the Post processing errors occurs there will not be any GI but the

Operation will be confirmed.

Solution: Check the Stock of the material. If Stock available the errors are removed

automatically. But for the particular material LG102510 there is no stock.


16/25

Ticket No:2010744

Description:please check why there is a difference between md04 and zccsr for material

l176939lx3 in PA2, unit LX01 ,in md04 the backlog requirement is 4 pieces, in zccsr the

backlog requirement (goods issue) is 70 pieces. please check where these 70 pieces are

coming from (maybe by debugging the program)

For the ZCCSR Report, the system calculation are as follows,

Req. Goods Issue = Sum of(Requirements + Receipts) at the MRP area.

Total Daily Req. = (Plant Requirements + MRP Area Requirements) for that Perticular date.

As the requirement in the dates (31/01/2012 ,27/02/2012 to 29/02/2012) are still exist in

the MRP Area (MD04) are together shown as Backlog in the critical shortage report..

Req-Goods Issue = Sum of(Requirements + Receipts) at the MRP area


17/25

Total Daily Req. = (Plant Requirements + MRP Area Requirements) for that Perticular date


18/25

Ticket no: 2046799

Description: The MRP doesn't work on the part number CC129425. There are only

requirements but no order planning are created by the MRP. When I do the transaction

MD03, I get the error message "Maximum number of order proposals per

deadline exceeded".

First place to check is the Material master MRP 1 View Lot Sizing Procedure & Fixed

lot size

As the Fixed lot size is maintained with lesser value if the requirement is more it creates more

no of planned order.Creation of planned order is limited by the SPRO IMG Settings

Tcode : OPPQ Click ERROR HANDLING.

Tcode: OMDV Click

Solution is to change the Fixed lot size value or Changing the LOT SIZING PROCEDURE


19/25

Ticket # 2084308

Description:While processing the COGI error the following error occurs Period for date

26.03.2012 cannot be determined from T009B (period variant Z4)

First place to check is Material master MRP 3 View fiscal year variant

Table T009b.

The error is mainly due to that fiscal year variant is not maintained with Periods.

Solution is below:

Maintain the Fiscal year variant or change it in material master.

In this particular ticket the fiscal year variant is maintained and the COGI is processed

without any issue.


20/25

Ticket No # 2090537

Description: Due to a change of the production versions the deletion of version K001 for Material

AZ201204 is not possible.

This is due to the existence of planned order with the Same Production version which will

allow deleting from the material master MM02.

But we can delete it from the C223 Tcode.

After deleting the Old PV, enter the new PV.

Delete the Existing planned order and Re Run the MRP. Planned orders will be updated with

New PV.


21/25

Ticket:2117124

Description:look at the order 8000323537, please. I thought a Topnumber ETN93958 with

the Status 20 (Exp. Prototype Build) can not be in a Production Order.

The Topnumber ETN93958 should not be in the production order 8000323537.

The component which has the Status 20 (Exp. Prototype Build) is copied into the Production

order .

For the Production Order : 8000323537, Corresponding Sales Order :3425590

If we look into the details of the Sales Order : 3425590


22/25

As per the Super BOM for the Material : 00W2L

For the Component : ETN93958, Obeject dependency is maintained as LX01_S_FH IN (8410, 8411)


23/25

The above mentioned Material :ETN93958 is having the Valid from Date : 30.01.2012 onwards,

which is currently valid as on date. So, the system will not stop in accepting this Material into

Production Order

Conclusion : If the corresponding Component in the Super BOM has the Valid From date, thatcomponet will be copied into Production Order, Even though the Material Staus is maintained as 20

(Exp. Prototype Build) This status, may give information message, during the creation stage.But, will

not stop the creation in selcting the Componet.


24/25

Ticket:2099189

Description:The product cost collector for the AZ81125 cannot be created correctly.

If we want to create the product cost collector the presetting in SAP is on "Production Plant/

Planning Plan".But is has to be "Production Version".

In KKF6N while creating the Product cost collector there is problem in Selecting the

Controlling level. Its Default we cant change it in KKF6n.

The T code to Change the Controlling level is check the settings with the T code:

CKMLMV_CA


25/25

It can be changed if there is no Planned order or anything else.

Documents

Tickets and Details