Status updation of Shop floor paper

Hi expert
I have created one Shop floor printout in Smart forms.i have created my own program.In the statndard printout
status will be changed to PRT when the print out taken.I want to in coperate this feature in my program also.
Please guide me
Regards
Manoj

All configurations are maintained properly in OPK8. The print program has been changed to SAPSprint.
Possible reasons or troubleshooting tips would be helpful.
Jibitesh

Similar Messages

Shop floor paper printing

Hi Team,
I am new to use the transaction OPK8. I need to configure to print production order details for shop floor paper printing.
How to use this transaction to print shop floor papers as per our requirement?
I need to print some BOM component details and kanban control cycle informations (eg: storage bin) in the shop floor papers. Is these informations available by default in OPK8 transaction?
I am beginner to use this transaction. So your valuable guidenace required.
Thanks
psk

Hi chandan
Priniting layout can be set on your for printing shop floor paper. The required field can be set from production.
Regards
J . Saravan

Production Schedule Profile & shop floor paper printing.....

Hi there ,
If we set the Execute Printing checkbox in the T-code <b>CORY</b>for a production scehedule profile....... then when we will release the order along with the other shop floor paper do the Transfer Order will also get printed if the material is warehouse managed.........
Please enlighten me .....
Thanks & Regards
Kaushik

Hi there ,
Thanks for your reply...... I am aware of the fact that the shop floor paper will be printed once the order is relased & the relevant config is done in the Production schedule Profile.........
But in case of the material which are warehouse managed the Transfer requirement will be created & the further the Transfer Order........... I wan tto know that these will also Print the Transfer Order doucment for the warehouse managed material .......
Thanks & Regards
Kaushik

What is shop floor paper ?

Hi,
Can someone explain in simple statement what is meant by a Shop floor paper in PP module ? An abaper is expected to change its layout and users can print it. Which programs are involved in sapscript ? What kind of changes are normally expected in the shop floor layout ?Thru which transaction I can print and verify the shop floor papers (like PO thru ME21N).
Would highly appreciate if u can answer straight rather than sending me links.
thanks

http://www.sap.com/industries/chemicals/pdf/BWP_SB_Manufacturing_Intelligence_Dashboards.pdf
http://www.honeycombconnect.com/downloads/PILS/OTE/13_12_06WhitePaper.pdf
Regards.

Incorrect sequence of shop floor paper after upgrade

Hi All,
We had an upgrade from 4.7 to ECC6 and we have a problem with shop paper printing for Production orders. The sequence of shop papers doesn't follow the sequence defined in configuration. e.g. Pick List gets printed before Operation list even though the configuration is otherwise.
What could be the possible reasons and solutions for such an issue?
Regards,
Jibitesh

All configurations are maintained properly in OPK8. The print program has been changed to SAPSprint.
Possible reasons or troubleshooting tips would be helpful.
Jibitesh

Shop floor Printing

I have made print setting in opk8 and it is working fine with one material , one order typeand one production order, where I can see preview of shop floor paper.
But when i make production order with same material , order type and same plant. Then iam not able to get print privew (when i press print option in menu FUNCTION.
I get message After the next update the order will be printed.

In my question , I hav mentioned that for same plant, same material, same and same order type, for one production order I can view print preview in CO02, co04 serveral times
But for other prodcution order, for same plant, same material, same and same order type iam not able to see print preview in co02 or co04. In that case, everytime i get message -After the next update the order will be printed

Shop floor with w/o no in PM module

Hi All,
Can you please explain me in understanding the **standard functionality** of Shop floor paper with W/O# in PM module.If possible please share document.
Regards,
Meghana

I guess, you are looking for smart forms which can be prepared from Maintenance order.
First in IMG, we need to define the shop papers which are going to be used for the order.
IMG => PM & CS => Maintenance & service processing => Maintenance & service orders => Print control
Under that, you can define the shop papers. Also custom shop papers can be added in that list.
Apart from that, based on order type, shop papers can be restricted. Based on user as well, shop paper can be restricted.
http://help.sap.com/saphelp_sm32/helpdata/en/32/da2e88713c11d58cd90000e8284931/frameset.htm

Shop Floor Statuses - Assign Shop Floor Statuses - Component Pick Release

Hi,
is there someone who knows the use of the following forms in WIP module:
- Shop Floor Statuses
- Assign Shop Floor Statuses
- Component Pick Release
We are in 11.5.10
Please provide also an example of a business scenario where this functionality could be used.
Thanks in advance
Regards
Riccardo

hi,
shop floor statuses are created which will allow/disallow moves and assigned to particular operations in the job.
they are normally used in OSP operations to control the movement of material thru intraoperation by the users when the material is gone for OSP.
and they can also be used to hold the job when its moving in operations (may be due to quality problems etc..)
Component pick release is used to issue the required components to a particular job based on pick slip report.
its another way of issueing material to wip apart from backflushing thru wip material transaction form.
hope that u can hav idea abt these.
if u need any clarifications, ols reply

What are the best ways (for best performance) in MII to process the incoming process messages from shop floor systems to SAP ECC 6.0 and vice versa?

Hi All,
Can you please suggest to choose the best ways (for best performance) in MII (12.2 on NW 7.3), to process the incoming process messages from shop floor systems to SAP ECC 6.0 and vice versa?
Thanks

Hi Surya,
Best practices for flow of data from ECC --> SAP MII --> Shop floor & Vice verse:
1. Send ECC data through IDOC's/RFC's as messages to SAP MII message listener and BSL transaction process data and update directly on shop floor database as if you configured in Data services or later send those data by web service to shop floor system (i.e. depends on Shop floor machines).
From Shop floor:
shop floor --> SAP MII --> ECC
1. Use either Web service or fetch data from DB and pass data to BAPI's for sending to ECC through BLS transaction.
Regards,
Praveen Reddy

Set user Defined Status in the Shopping Cart

Hello,
I am facing problem while Setting user defined Status in the shopping cart. Below are the steps which I have followed.
1. I have created Status profile via Transaction 'BS02' and also created the Status 'On Hold' with Status number 'Exxxxx'.
2. Entry of this external status is also created in the table TJ30.
3. Also I tried assigning this Status profile in Transaction type for "BUS2121".
After making the above configuration for the new User defined status I have used below function module in my program.
I am using FM "CRM_STATUS_CHANGE_EXTERN" to set the User defined status in the shopping cart.
CALL FUNCTION 'CRM_STATUS_CHANGE_EXTERN'
    EXPORTING
      objnr                    = ls_header-guid
      user_status          = lv_stat
    IMPORTING
      stonr                    = lv_stonr
After this FM I am also using "COMMIT WORK AND WAIT ".
But still my Status is not updated in the Shopping Cart.
Expert please suggest if some one has work in this scenario.
Best Regards,
Chirag Shah

Hi Chirag,
try to initialize Status schema before update.
CALL FUNCTION 'CRM_STATUS_OBJECT_CREATE'
     EXPORTING
       objnr                        = ls_header-guid
       obtyp                        = 'SCH'
       stsma                        = 'ZHOLD'
     EXCEPTIONS
       obtyp_invalid                = 1
       status_object_already_exists = 2
       stsma_invalid                = 3
       stsma_obtyp_invalid          = 4
       error_ocurred                = 5
       OTHERS                       = 6.
Regards
K

Printing Shop floor documents

Hello Experts,
Is it possible to print the shop floor documents in production order status CRTD ?
If yes what are the settings to be done to get printing before releasing the order?
Regards,
Jejesh
Edited by: jejesh yal on Jan 27, 2009 6:47 AM

Hi,
As per Standard SAP Practice, It is not possible to print shop floor papers befere release of Production Order i.e. It must have status REL and not CRTD.
You need to maintain following settings for Printing Shop Floor Papers :
In OPK8
Name of the list - LG01, LG03, LK02, LV02
Spool parameters - User and plant = *
Reference operation - type - *, ref order = your order type
Forms -
LG01 - PSFC_OBJECT-LIST
LG03 - PSFC_ZUGL-LIST
LK02 - PSFC_GOOD-ISS-SL
LV02 - PSFC_CONF-TICKET
Print Programme -
LG01 - PPPROBJU
LG03 - PPPRZUGL
LK02 - PPPRWARS
LV02 - PPPRRUEC
List control for transaction
ref order type, plant, MRP controller-*
transaction codes - CO01, CO02, CO03, CO04, CO05, CO07
Flow control for transaction - all are online
Hope this helps.
Regards,
Tejas
Edited by: Tejas Pujara on Jan 27, 2009 6:55 AM

Status update for MeeGo on the N900

Here's a copy of the text sent by Harri Hakulinen from Nokia. He is the project lead for MeeGo on the N900. This message was sent to the MeeGo developer mailing list just now:
Hello MeeGos !
This is brief status update of "MeeGo to N900" project. This project is currently running as Nokia project, and I am Nokia project lead for it. The current closed mode of development is not the target for us at all, but rather transitional condition. As already discussed by Valtteri in TSG meeting, we are looking into going more open mode shortly. One reason why we have done this on this way is that at the same time we have been trying to handle opening of many currenly closed components that are needed in MeeGo and to build feasible MeeGo images for N900.
However, a lot of related work is already done completely open, you can find more info from places like ofono.org, connman.net and meego.gitorious.org . So if you are eager to contribute or want to closely follow whats happening, please work on those.
As you know, we have delivered working MeeGo images for N900 as part of first code drop in the end of March. At that state we were using older kernel version on N900 than on Atom side, as we used the same kernel (.28) than what is used in Maemo 5 based products today. We ended up doing that simply because lack of time to contribute and port all the drivers to the newer kernels.
Now, for the upcoming May release of MeeGo, we are going to use the same kernel version (.33) than Atom based devices are using. For that we need to submit number of ARM-architecture patches to MeeGo as well, because many of the required ones have just been contibuted upstream kernel and were not available in .33 version originally.
We have already enabled most of the main drivers, like LCD, GFX, Wlan and BT. Still, there is a lot to do in order to enable .33 on N900, like audio drivers, and modem subsystem including SSI buss driver, modem data and audio drivers etc. Our adaptation guys are in fact contributing those modem subsystem related drivers as we speak, and if you are following kernel mailing lists you can see how that goes on.
Besides of enabling the new kernel, we are working with number of smaller and bigger issues for N900. Starting from the beginning, we are now based on ARMv7 combiled code, so the code should be better optimised for N900 now. ARMv5 compilation that was in use for code drop will still be there, and it also seems to be used at least by community project that is planning to release MeeGo for good old N810 tablets
Also, we are planning to enable dual booting of Maemo 5 and MeeGo for the upcoming release. So that will be offered as 3rd way to setup MeeGo to N900, including the existing "native" MeeGo only on N900 and chroot based MeeGo on Maemo 5 setups. Taking the dual boot mode into use likely includes upgrade to Maemo5 kernel as well, but that should not be big issue in the process of enabling that.
As I don't want to go ahead of others working on MeeGo architecture and other issues I will stop now, but I will report again when we have more to tell about the subject.
Br,
// Harri

Here's another update..
It seems that MeeGo on the N900 is not directly being driven by Nokia! It's an open project.. so the net result is MeeGo on the N900 may look and feel very different to Meego on the N900's sucessor
Either way, I'm certainly greatful for their efforts!
Hello Meego's,
As indicated in my previous mail about "MeeGo for N900" status, we were planning to open up our MeeGo work around N900. Now I am happy to announce, that we are there
First, to make it absolute clear for everybody: This is about open MeeGo adaptation to N900 device.
Like any other MeeGo project, it is open source project for all applicaple purposes, and does NOT directly have links to any potential Nokia product or potential product plans. So, based on this or any other of my posts, please do NOT start or continue speculation of upcoming Nokia MeeGo releases. That is practically not helpfull, and mostly only takes our time when we need to explain our words and actions in detail to various directions.
From our part, we are trying to implement the open development model that has been discussed now so many times around MeeGo. On practical terms, we are trying to work based on proposal by Carsten Munk, see
http://wiki.meego.com/Proposal_for_Best_Practices_for_working_in_a_MeeGo_team
We have already created some resources that will be used by the team, you can learn about those and the upcoming ones from http://wiki.meego.com/ARM/N900. We have IRC channel for realtime discussion, we will use meego-dev mailing list for normal discussions and announcements, and we will have Gitorius project for code.
We will evolve our practicies during the work, so if you are interested, stay tuned to those channels. I belive that soon we are also able to figure out, what is best way for community members to help us in development, and then effectively be part of the team.
I would also like to use this as opportunity to introduce the team behind this work (so far) and also thank them about their hard work and long hours. We have team that consist of some Nokia subcontractors and also growing team of Nokia personel:
"MeeGo for N900" team (so far)
- Cybercom Turku team; Marko Saukko, Jouni Peltonen, Sami Sirkiä, Jari Smura and Luka Milovanov.
- Cybercom Tampere team; Kalle Lampila,Teemu Tuominen,Tuukka Mäkinen and Ville Marjusaari.
- Carsten Munk via Nomovok
- Jarkko Nikula via Atomide
- Jan-Simon Möller from Linuxfoundation
- Nokia team; Alexander Kanevskiy, Felipe Contreras, Markus Lehtonen, Ameya Palande, Sakari Poussa, Roger Quadros and me.
In addition to official project team, many Nokia people have helped us despite their hectic daily work, even with their free time. Most of them are driven by the desire to open, repurpose and upstream all relevant sw that has been originally created for Maemo 5 based N900 product during previous years.
Marko, Jouni, Sami & Luka and Markus were working with me already on last year when we did prototypes and interoperability tests of Maemo & Moblin stuff combined in different ways. Based on those we had pretty good picture of what we are doing and why.
And of course, we have had very good and productive co-operation with various Intel teams since those times. Anas Nashif and many others from Intel's MeeGo team have done a lot for us by enabling ARM stuff in MeeGo OBS and repositories.
Last but not least, I want to give special thanks to Stskeeps (alias Carsten Munk . He has teached us how to operate on open, and he has also done respectable amount of this work since early days of Meego. In addition to that, I belive that his earlier work on Maemo community and on Mer project has in fact inspired all of us and shown a way to MeeGo alredy years ago.
Br,
//Harri

Open item in PS reporting for shop floor order (same as PO's or PR's)

Hi Guys,
I have a question simple but I could till now find any solution in standard Report Writer or in Report Painter and I donu2019t want to create a specific report with an ABAP.
In the system we have set quit complex projects with WBS, Networks and Activities. In each project there are also material which are standard material consumed from collective stock and specific material produced internally or purchased externally. The specific material are consumed through specific stock project.
In Report Painter/Writer there are ratios for the open line items for purchase orders or requisitions but I am not able to find the same values for the shop floor orders made internally. Further I get the values for the planned shop floor orders and of course the complete actual (coming from both requirements) but I will know what are the values which are between (nat yet actual and plan).
Has anybody already faced this situation or do anyone the solution to my problem?
I thank you for your replies.
Best regards

Hi
Please use table EKAB for your search instead of using EBAN Or EKKO
Thanks & Regards
Kishore

Unable to run bapis for project status update and date update together

Hi Experts,
I have a requirement to update the dates and status of a project WBS at level 4. I am trying to do update the CJ02 Transaction using standard BAPI available. I need to do both Date update and status update in the same LOOP PASS   i am using the below mention bapi. when i am doing so i am getting an error Project 'A._____' has been currently processed by ID i.e. my id.
I have tried putting a wait for 2 seconds in the code but its still not working. please find the order below in which i am calling the bapi.
Loop at itab.
if date_changed = 'X'.
      CALL FUNCTION 'BAPI_PROJECT_MAINTAIN'
      READ TABLE it_error WITH KEY message_type = c_e.
      IF sy-subrc <> 0.
Commit
        CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
             EXPORTING
                  wait   = c_x
             IMPORTING
                  return = s_ret.
   endif.
endif.
if Status_change = 'X'.
      CALL FUNCTION 'BAPI_PS_INITIALIZATION' .
      CALL FUNCTION 'BAPI_BUS2054_SET_STATUS'
      READ TABLE t_result WITH KEY message_type = c_e.
      IF sy-subrc NE 0.
        CALL FUNCTION 'BAPI_PS_PRECOMMIT'
             TABLES
                  et_return = t_ret.
        CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
             EXPORTING
                  wait   = c_x
             IMPORTING
                  return = s_ret.
     ENDIF.
endif.
    WAIT UP TO 4 SECONDS.
endloop.

Try to use
SET UPDATE TASK LOCAL.
before each BAPI call.
Did you try to debug through your code, leaving sufficient time between BAPI calls? If it does work like that, then the above statement might help.

Delivery status update in sales document at PGI

Normally system updates the delivery status of sales document line level, when a delivery document is created with respect to that sales document line.
But I want system to update the delivery status (in sales doc. line) when PGI is done for respective delivery document; not at the creation of delivery document. Below I have shown the status updating scenarios that I expect.
Scenario 1
Sales doc line qty: 100 PCs
Delivery Doc qty: 50 PCs
PGI: Not done
Status in Sales document line should be A (Open)
Scenario 2
Sales doc line qty: 100 PCs
Delivery Doc qty: 50 PCs
PGI: 50 PCs
Status in Sales document line should be B (Partially delivered)
Scenario 3
Sales doc line qty: 100 PCs
Delivery Doc qty: 100 PCs
PGI: 100 PCs
Status in Sales document line should be C (Fully delivered)
Can anyone propose a possible way of doing this (configuration/ user exits/ BADI etc,)?
Thanks,
Ramindu

Hi,
I dont know it with the use of ABAP development, but by functional logic, can suggest you to configure the rush order sales configuration for your particular sales order.
just check that availability of that particualar sales order is met or not prior to it.
and then automatically when your delivery doc is created, PGI would be done and the status of your sales order would be updated with it.
try it out on your development client, if it works out.
regards,
Siddharth.

Status updation of Shop floor paper

Similar Messages

Maybe you are looking for