Question:
Hi,
Using source inspections with batch management. No problem in creating Inspection Lots. However if there is no batch no UD can be made. So we can either ;
1. Create batch in Purchasr order. This correctly associates the batch with the inspection lot.
2. Create the batch manually before UD.
1. is best above using the PO. However, this does not create the classification view on the material.
Any ideas anybody how to get round this.
Answer:
Nope, you pretty much got it! Why are you worried about classification at that stage (PO)? You should have classification set up to automatically happen at GR time or at time of UD.
_________________
Available for spot consulting, troubleshooting, remote configuration/consulting and teaching. 10+ yrs in QM. Primary focus on Pharma and Chemicals.
Answer:
Because the UD is being written to a characteristic for some other functionality.
Answer:
I mistyped the first problem. I meant to say the classification view on the batch.
Also if I create the batch manually with MSC1N then the view is created.
Answer:
I mistyped the first problem. I meant to say the classification view on the batch.
Also if I create the batch manually with MSC1N then the view is created.
I don't have a delivery at Source Inspection. I am approving before delivery but cannot do the UD because it errors because the classification view is not there on the batch.
Answer:
Ok.. I'm more confused then before. UD does not error if batch classification is not done for the batch already. UD will cause batch classification to happen. But the UD can't be done if there is no batch.
And if you want to use the UD to write to a characteristic for some other functionality as you said, then you have to have the batch created already to have a place to write the value to! In which case then, doing the UD shouldn't be a problem.
Am I lost here? Seems to be a chicken/egg question!
_________________
Available for spot consulting, troubleshooting, remote configuration/consulting and teaching. 10+ yrs in QM. Primary focus on Pharma and Chemicals.
Answer:
Sorry, have been away on vacation.
I said that the UD does error because the classification view is not on the batch and if the batch has been created at the PO then the classification view is not created with the batch.
So to recap,
I raise a PO which needs a source inspection.
I create a batch number on the PO and the batch is created (does not create the classification view on the batch).
A source inspection is done.
The UD errors because the classification view is not there on the batch. I have to manually edit the batch record and create the classification view.
Answer:
Ok.. Try this. This is found in configuration
Logistics - General-->Batch Management-->Batch Valuation-->Valuation for Creation of New Batches Using Function Module-->Set Up Customer Exit for Activating Batch Classification.
Below is the help file info from this. You could use this to force the classification when the batch is created. I still don't think you have to. You are creating a classification view in the material master right and assigning the material to a class? I still think your classification should happen automatically when you create the batch.
Set Up Customer Exit for Activating Batch Classification
You can use function module exit EXIT_SAPLV01Z_012 in SAP enhancement SAPLV1ZN when assigning characteristic values to batches. You use this to determine the type of classification (online or in the background, for example) when creating a new batch with the central function module VB_CREATE_BATCH.
Further Notes
When creating the batch with regard to a reference batch, the assigned values of the corresponding characteristics are copied.
The batch material, or at least one batch of the material must be assigned to a class so that the batch may be classified.
In the exit, you can use a communication structure with the application data for the respective business transaction (for example, plant or material type). If you require further information, you must obtain it yourself in one of the user exits (such as time, user name, or date, for example).
Activities
1. Create the enhancement.
Create also either a new project or use an existing one.
2. Activate the project.
Your enhancement is only effective after you have done this.
Further Notes
Unlike modifications, enhancements are release-insensitive as they are not located in the SAP original but in a name range reserved for customers.
For information on the general procedure for creating enhancements, choose "Utilities - Manual".
Each enhancement is documented. To access this documentation, choose "Display SAP doc" in the enhancement.
_________________
Available for spot consulting, troubleshooting, remote configuration/consulting and teaching. 10+ yrs in QM. Primary focus on Pharma and Chemicals.
Answer:
Hi Craig, Thanks for that I will have a look. I agree with you that it should happen when you create the batch. Just happens that I am creating the batch when I raise the PO from transaction ME21N which is quite legitimate and should create this view from here . In all other transactions it appears to create the view correctly.
Thanks
Answer:
Let me know what you discovered on this! I'm really curious as to how you resolve this one.
BTW: For those folks interested, the above mentioned user exit is really supposed to be used to populate characterisitcs with values for the batch at time of classification that can be done progamatically. For instance, copying a value from a material class characterisitic or other class type into a batch characterisitic so it can be printed to a COA. Maybe filling in the name of the user receipting the batch into a text characterisitic on the batch. Possibly time stamp as well.
_________________
Available for spot consulting, troubleshooting, remote configuration/consulting and teaching. 10+ yrs in QM. Primary focus on Pharma and Chemicals.
Answer:
Hi :
I am trying to use Enhancement SAPLV1ZN, in the context of creating a new batch with reference to another batch. We have implemented EXIT_SAPLV01Z_014, which is working for the non-QM Classification data (such as our GR Date for Batch Determination based on FIFO), but we are not able to successfully get the values for the QM Characteristics copied. We have worked with EXIT_SAPLV01Z_012. which seems to have a switch to transfer the QM Characteristics, but this is not working for us. Do any of you have any ideas why the QM Characteristics might not be copied?
We are calling the CFC's (for SAPLV1ZN) from the Functions VB_CREATE_BATCH & VB_CHANGE_BATCH, and these are both being called by BAPI_BATCH_SAVE_REPLICA.
Can anyone help?
Answer:
First off I'm not an ABAP'er so I will have limited info on this. But exactly what are you copying? The enhancements don't just automatically "do" stuff for you. I assume when you mention the date for GR, your referring to one of the LOBM standard characteristics. These wouldn't be 'copied', they are just part of normal standard SAP so I'm not surprised you see values.
You don't say what your copying from or anything.. Another batch? How is the user exit to know which batch? Did you add code to it to tell it what to get? Which characterisitcs to copy? etc..
_________________
Available for spot consulting, troubleshooting, remote configuration/consulting and teaching. 10+ yrs in QM. Primary focus on Pharma and Chemicals.
Answer:
Hi :
First of all...WOW...Thanks for your quick response. Maybe you saw my post yesterday regarding the "Batch Derivation" functionality being available in 46C. What we are doing is copying the values of Batch A to Batch B/C/D, which are either being created or changed, upon the Usage Decision. We have created a copy of BAPI_BATCH_SAVE_REPLICA, and assigned it to a follow-up action during the UD. We just did a first test, after developing the core functionality outside of QM for 1 1/2 days, in QA11 at the point of recording the UD, and it works fabulously.
We provide the BAPI with the Material Number & Batch, from which to copy the data, and then it copies the data to the newly created or changed batches which use the same batch number as the source batch, but of course with different materials. These are typically Packaged Materials (SKUs). We programmed a logic into the Function Module, so that it knows the materials which to "push" the batch data to, according to the product hierarchy.
The QM Charactersitics are currently being copied, as well as all the MCH1 data, but the problem is that the values which are assigned to these QM Characteristics are not being transferred. I assumed that once we set the flag in EXIT_SAPLV01Z_012 as explained in the documentation, You can set the parameter NO_CHECK_OF_QM_CHAR as follows:
SPACE -> The characteristics offered for maintenance do not include the characteristics supplied via QM
'X' -> The QM characteristics are included in maintenance
that the corresponding QM Values would be copied into the "destination" batches from the "source" batches, but at this moment, this is the only point that we need to solve to have this solution working correctly.
I hope that this answers your question, and thanks in advance for any insights that you might be able to provide.
Answer:
Cool.. I'd say that at this point you have enough to submit an OSS note on it. Of course, don't be surprised if SAP says the batch derivation is not supported in 4.6c and that is one of the features not completed in 4.6c!!! (based on your other posting about it's use in 4.6c)
_________________
Available for spot consulting, troubleshooting, remote configuration/consulting and teaching. 10+ yrs in QM. Primary focus on Pharma and Chemicals.
Answer:
Hi :
I guess that I confused you by talking too much about the hidden "Batch Derivation" functionality in 46C. My current problem is that the in Enhancement SAPLV1ZN, the QM Batch Characteristics are being copied, but the corresponding Values are not. Has anyone implemented this Enhancement before, who might be able to offer me some hints as to what we might be missing?
Thanks.