fbpx

SCAL- Calendar Maintainence

by

In SAP the Factory calendar maintainence is done through the T.code SCAL.

This is one of the important configuration that needs to be given more importance.

1.SCAL – configuration details:

This has 3 important settings inside the SCAL
1.1) Public Holidays – Defining the public holidays is important. Inside this you can define what type of public holiday. This can be used in one or more Holiday calendars.

1.2) Holiday Calendar – You can define a holiday calendar and use the created public holidays insdie this so in the next step when you create a factory calendar this can be used in one or multiple Factory calendars. 

1.3) Factory calendar : You will be creating the factory. Here you will be using your Holiday calendar ( not mandatory) to define the holidays. Then also defining the workdays. 

Example: Global – Monday to Friday will be working day
                  Middle east – Except Friday all days will be working day.

You can also define special holidays when there are unplanned holidays etc.

2.Assignments: 

1) This will be generally assigned to the Plant configuration which will be treated as Plant Factory calendar. Used in all places in PP,SD,MM etc.
2) This will be also used in the Shipping calendar.

3. Any modifications: 

1) Normally the modification or changes will be directly done in the respective client.
2) It can also be moved through the transport mode, but when it is transported it does not move the changes done in the particular plant, it moves all the changes done in the other calendar also. So this method is generally avoided.

4.Important:
1) When any change is requested for a particular calendar ensure that this is used only in that particular plant.
2) Also check this is not used in the shipping calendar, which will be assigned in the shipping points.( T.code -OVXD / Table -V_TVST).
3) Also we need to check if it has been assigned to any Route also. The below table dispaly will help to have a quick look on the assignments.
V_TVRO_COM
V_TVST_ROF

In case of this kindly update the requestor of the usage in other plants and shipping points and impact of the same and make the required modifications.

  

Capacity Planning error during Prod order creation in Finite scheduling.

by

Message no. CY298
No reqmts/caps exists or not relevant to finite scheduling

Procedure
Assign capacities to the work centers affected by the order.
Set the indicator Relevant to finite scheduling at the capacities in the work centers affected. ******************************************************************************

Message no. C2053
Operation does not have capacity requirements
Procedure
Check the operation and the corresponding work center.
There are no capacities defined at the work center at which the operation is carried.
The control key of the operation specifies that no capacity requirementsare created.
The operation has not been scheduled.
******************************************************************************
When i faced the  above errors i checked all the above procedure and interestingly , the capacity requirement calculations Formula key did not  have the selection fo the check box in the 
work center is allowed for capacity requirements.

After maintaining this  i was able to  generate the capacity for the production orders and same displayed in all the evaluation T.codes.

PDC-SAP Production Confirmation Interface Design

by

In case if we have a PDC system and the confirmation is done from te PDC system then the below is one approach which uses most of the standard features of SAP

1) The data from the PDC system can be passed to the SAP and placed in a application server dedicated location  / folder.

2) Whenever the file is placed an event can be triggered to get a job started .

3) This job needs to have a customized program to trigger an IDOC. You can use the IDOC method PPCC2PRETTICKET to process this data and generate an IDOC

4) Once the Idoc is placed it will be processed immediately, configure the message type accordingly in the partner profile

4) This message type will not post the confirmation, we have to again run the CORUPROC1 program, which will help to post the goods movements.

5) In case of the post processing use  the CO16N – Confirmations to reprocess the error things.

This is a high level plan this has to be coupled with event to automatic triggering of the jobs and other process.

The sequence of activities is to be given more care.


FILE – Logical File Path Vs Physical File Path

by

Many times we work with the logical file path and also physical file path. I like to make this post to have a over view on both the Path.

You should be aware of the Transaction code: FILE.

This is the T.code which help you to map both of them

Logical File Path: 
1) This is not physical, it is only a representation of the physical path. Generally the physical path will have the folder representations so to make it simple it is being used.

Physical File Path:
1) This represent the details of the folders/file which can be seen on the application server.

This. FILE t.code helps to map you between them and also other functionalities.

Hope this helps to start with the T.code..

   

Period End closing -2

by

When we are moving from one period to another and during production confirmation, we will face few errors due to the period not open.
The below will have few of the errors which are common and way to over come it.

 1)Message no. F5201
Posting period 002 2013 is not open
T.code: OB52 – Ensure that the period is open for the curent period.
 Diagnosis
Period 002 of fiscal year 2013 is not open for posting for the variant of posting period XXX.
2)Message no. F5286

Period 002/2013 is not open for account type S and G/L xxxxxx
T.code: OB52 – Ensure that the period is open for the curent period.

3)Posting period 005 2013 is locked (check posting date)
 Message no. RU428

This above error may be due to the reason that the CO period is not open. IN such case kindly inform the CO team or use the OKP1 t.code to ensure that the posting in that period is allowed.

4.) In plant XXXX , post to current period 20xx /xx
Message no. M7037
 Please check for the posting period(MM) open in the MMRV/MMPV.
 In case if it not open and disallowed in backdatig posting, then this issue will raise.

 Do work with the MM team on this issue.

Note: Kindly Ensure that above T.codes are all done in confirmation with the FI/CO/MM team members.

IDOC-Basics – 2

by

IDOC STATUS – 64 ( for inward idocs)

As we deal with idocs, the idocs will get posted to the
sap system with status 64.

once the status is set to 64 to process this idoc to the
next step, we can use the program RBDAPP01.

RBDAPP01-This program can be used scheduled in the background in periodic schedule.

IDOC STATUS – 51( for inward idocs)
RBDMANIN- This report attempts to post the inbound IDocs with
status ’51’ (Application document not posted).

As we work with the idocs, when the idocs are processed and they may be not posted
for various reasons.when you wanted to re process this idocs this program
can be scheduled periodically.

The ‘Import in background’ checkbox has the following significance:

If the checkbox is marked, the IDoc processing is triggered
immediately without the IDocs being displayed. Following the processing, a list of the IDoc status values is output.

ID0C STATUS – (2/04/05/25/29 outwards)
You can use this program RBDAGAIN to schedule job to reprocess the Outward idocs.

SAP Implementation – Textile Mill- Part 2 ( Cotton-Ginning)

by

Business Flow:
The first process in the formation Cotton fabric formation is the preparation of the raw material.
cotton is the raw material for the cotton fabrics. We knew that the cotton is cultivated in various parts of the world and the flower is collected from the plan by the farmers and bundled in raw form and send to the ginning units.

There are different varieties of the cotton and few of the important parameters that is important to segregate the cotton is based on the Staple length,Moisture,Maturity level etc. Based on this these are segregated and processed in the gins and packed separately.

This processing is called ginning. In this process the main activity is to remove the impurities from the cotton without affecting their basic properties. Lot of dust,Husk etc which is there in the cotton needs to be removed and then bundled in BALES.

source: http://journey2textile.blogspot.in

SAP – Process mapping:

* This entire flow generally is kept simple.
* You will have simple BOM with raw cotton and processed cotton in the Output.
*  The material codification for the output will be kept simple so that it can be identified easily
* We can work with a discrete environment and Production orders can be created on a monthly basis.

SAP Implementation – Textile Mill- Part 1

by

Hi,

I always had in the mind to post my experience with various industries on the SAP implementation.I have been part of the implementation team for a Textile, Garment,Autombile(OEM),Autocomponent manufacturer (Tier1 Supplier for OEM),Publishing company,Consumer Products,etc.
Recently there was request from one of my friend to know about the Textile industry process.So it has lead me into this Post and for the subsequent posts that i planned to write. I wanted to start with Textile industry
since my career in SAP started from the implementation of SAP for the Textile industry. Luckily i was into a project which was composite textile scenario.

When i mean composite, they were composite in the Business. They had all the manufacturing facilities from Spinning -> Dyeing ->Weaving->Garment. And they were in wide range of End products like Cotton,PC,Cotton dyeing and Polyster dyeing.

I have planned to have a series of blog on this topic and currently i really dont have much of the numbers but to start with i have put the Part 1.
And i will go with mostly on the Weaving, Dyeing etc since i have been more inclined towards this business.
In this Textile mill series i will be covering up on the spinning, Weaving,Dyeing,Fabric Finishing process.
In SAP terms it will cover on the scenarios like
 MTO, MTS, MTO with Variant configuration, MTS with Material variant etc. I will try to be honest to write all the subjects i knew and the issues we faced on this.
keep watching this blog, your comments are very valuable.

Reduced Qty in REM Planned orders.

by

Reduced Qty in REM.

Generally in the REM scenario, we will have the planned order and this planned order
details will disappear from the PLAF table once the planned order quantity is completely produced.

When the planned order quantity is available or partially confirmed , the reduced qty is available in the table PLAF – field ABMNG (Reduced quantity).

Some times, this information will be helpful to produce some reports to monitor the situation of the planned order.

I wanted to share this, as i came to know about this very recently.

Again, once the planned order is completed we will not have traceability. So this will he helpful till we have the Planned order in the system.