|
Share this post:
|
|
Applying Hot Packages Using OSS --> http://www.zshare.net/download/108784843d8fce82/
|
Share this post:
|
|
Transaction SARA contains all the SAP archiving objects for all the SAP R/3 applications modules. All the SAP archive functions are shown in SARA. Choose the corresponding SAP archive object, hit enter and the archive administration menu will be shown. Provided here will be an example on how to archive the SAP Material Master.
Archive a Material Master Record
When a material is no longer required in a company or plant, you can archive and delete the material master record.
You have to Flag the material master record for deletion. This is known as logical deletion.
Before a material master record can be archived and deleted, other objects (such as purchasing documents) that refer to this material must themselves be archived. You can see which objects these are and the dependencies between them in the network graphic.
If a material master record cannot be archived and deleted at a given organizational level, the reason is given in the log (for example, a purchase order exists for the material). The log also contains technical data such as the number of material master records read and the number deleted.
Some of the archive error log message :-
Archiving object MM_MATNR for archiving material master records.
You can display the archived data, but not reload it.
To archive the material master, first goto transaction MM71.
Type in a variant name and click Maintain. (Tick the Test Mode for archive simulation).
Save the variant.
Maintain the Start date and Spool parameters and click execute.
Click Goto Job Overview to check the archive status.
To do a permanent delete, goto transaction SARA and click Delete button.
Maintain the Archive Selection, Start date and Spool parameters.
Click Test Session for testing or click execute to start the deletion program.
Click Goto Job Overview to check the delete status.
Now, if you goto MM02/MM03, you will not be able to find the record in the material master.
|
Share this post:
|
|
Material Determination is used to swap one material for another.It is possible to get a list of materials for substituiton,but remember you can substitue only one material from the list.
This can be done through substituiton reason T Code [OVRQ]
See the substitution reason number for Manual Material Selection
- check the Entry box
- check the Warning box
- select A for Stategy
- save.
Go To VB11 to create Material Determination (taking into consideration that all the previous steps for material determiantion i.e. maintaining condition types,maintaining procedures for material determination and assigning procedures to sales doc. types have been done)
Create one material determination,dont forget to give the Subst reason on top and also on the line.
Click the Variants Icon on top left-Sreen opens
Specify different materials you want to swap with the material you have enterd
Note that the subst reason is already copied on the screen
Remember materials should be of the same sales area,atleast Divisions should be same
|
Share this post:
|
|
Archiving the Material Master
Transaction SARA contains all the SAP archiving objects for all the SAP R/3 applications modules. All the SAP archive functions are shown in SARA. Choose the corresponding SAP archive object, hit enter and the archive administration menu will be shown. Provided here will be an example on how to archive the SAP Material Master.
Archive a Material Master Record
When a material is no longer required in a company or plant, you can archive and delete the material master record.
You have to Flag the material master record for deletion. This is known as logical deletion.
Before a material master record can be archived and deleted, other objects (such as purchasing documents) that refer to this material must themselves be archived. You can see which objects these are and the dependencies between them in the network graphic.
If a material master record cannot be archived and deleted at a given organizational level, the reason is given in the log (for example, a purchase order exists for the material). The log also contains technical data such as the number of material master records read and the number deleted.
Some of the archive error log message :-
Archiving object MM_MATNR for archiving material master records.
You can display the archived data, but not reload it.
To archive the material master, first goto transaction MM71.
Type in a variant name and click Maintain. (Tick the Test Mode for archive simulation).
Save the variant.
Maintain the Start date and Spool parameters and click execute.
Click Goto Job Overview to check the archive status.
To do a permanent delete, goto transaction SARA and click Delete button.
Maintain the Archive Selection, Start date and Spool parameters.
Click Test Session for testing or click execute to start the deletion program.
Click Goto Job Overview to check the delete status.
Now, if you goto MM02/MM03, you will not be able to find the record in the material master.
|
Share this post:
|
|
For SD material Determination you can create a Substitution reason and on the Strategy field, the following info. is available:
Product selection in the background is performed on the basis of the availability check.
We want to have the material determination only in case on material shortage. We expect the Substitution reason to give us this functionallity. It does not hovever take the availabilty into account before substitution.
We thought the worse case is to create a ABAP which is linked to the "requirement" field in the Procedure (OV13).
Has anyone had the same requirement? Is this a bug or just incorrectly documented?
I also encountered this abnormally recently using material determination. In order to combat the problem, the first product substitution should be for the original material. I've illustrated this below:
Original Product: ABC
Substitutes: DEF, XYZ
In order to perform product substitution ONLY in the case of ATP failure for product ABC, structure the Material Determination record as follows:
Material Entered: ABC Substitutes: ABC
DEF
XYZ
There seems to be a devaition at availability check and or on a conceptual note still.
Availability check can be configured both at requiremnt class and at the schedule line categories level.
Whilst the availabilty check at the requirement class level via global and mandatory configuration the schedule line catgry availability check deals with the order.
It is mandatory that the reqmnt class is flagged off for avlblty check and the schdelu line cat need not be.
The following are the mandatory for Availability check to happen--
1. Must be swithced on at the requirment class level and at the schedule line level.
2. Reqmnt type must exist by which a requiremnt class can be found
3. There must exist a plant and is defined
4.Checking group must be defined in Material Master records(it controls whthr the system is to create individual or collective reqmnt)
A combination of checking gropup and checking rule will determine the scope of availbaility check.
