Importance of batch status management.

Hi dudes,
Please explain me the need of batch status management activate and what is initial status of batch.
Please explain with an example.
thanks in advance
Robert.

Hi Robert,
please see help.sap.com
http://help.sap.com/erp2005_ehp_03/helpdata/EN/25/283a594f7811d18a150000e816ae6e/frameset.htm
Regards,
Sabine

Similar Messages

Batch status Management Active

Hi SAP Gurus!
We have SAP implemented in our organization 4 years back and from that time Batch status Management is not active in our system.
Now, we want to activate batch status at Plant level. So, that for any certain plant we can manage it through batch status management. Our material batch is unique at clienet level.
Any material X - Plant 0001 - Batch B1
material X - Plant 0002 - Batch B2
How we can activate batch status management for above scenario. Also, I want to know if client level batch status management is active irrespective of plant, then what will be settings and impact on business.
Kindly let me know the details about different settings and busines imapct. Stepwise settings will help much to me.
Thanks in advance.
Regards
roys

the status managment correlates with teh batch level.
if the batch level is client level, then the batch is unique in your system, in whatever plant you have this batch, it is the same material and same batch.
if you change the status of this batch from unrestricted to restricted, then you effect inventory in all plants that have this batch.
http://help.sap.com/saphelp_46c/helpdata/en/25/283a594f7811d18a150000e816ae6e/content.htm

Batch status at recurring insp lot creation

We have setu recurring insp 09 for few materials. We use "insp stock at creation" option. So system work as expected and create lot and put stock in QI, but still batch status remain "unrestricted". Our req is at the time of lot creation it self system should set batch status as "restricted". How to setup it?
When system setup "restricted" status for recurring batch? Help appreciated.

check option
Recurring Inspection: Block Batch at Lot Creation
Specifies, that a batch is blocked, when the inspection lot is created, if the inspection date lies within the opening period.
Use
If you choose this option, batches are blocked, if their next inspection date lies within the opening period:
If the batch status management is active in the corresponding plant, the batch status is changed to "restricted".
If the batch status management is not active in the corresponding plant, the batch stocks are transferred to the blocked stock.
If the batch status has changed or a transfer posting takes place, a new inspection lot is created for each storage location.
If a relevant inspection lot already exists and the next inspection date has already been reached, the change of the batch status or the transfer posting also takes place

No request generated for batch status active/ inactive settings

Dear Experts ,
When is make the status "active " for batch in IMG , Logistics general , Batch management , Specify Batch Level and Activate Status Management,Define Batch Status management , THE SYSTEM DOESNT ASK FOR A REQUEST .
Plsease tell em if it is ok for the system to NOT TO ASK FOR A CHANGE REQUEST ?
IF yes , please let me know if we need to directly make the above settings in the [production server ???????
Regards
Anis

any response ?

Error-IM258-Object does not exist (Status Management)

Dear All
We have used the enhancement "MCI10001" for triggering the external E mail while scheduling the maintenance plan using T code IP10.
System will fetch the E mail ID from the equipment master -partner function either Vendor or User responsible and sends the mail
But while executing IP10 system throws an error message as follows
Error Msg no: IM 258- Object does not exist (Status Management)
This refers to an error in central status management.
Kindly help on the above issue
Regards
Thyagarajan

l have same problem my code below
help me please .
if email is not INITIAL and ulke is not initial and sy-tcode eq 'QM01' and sy-ucomm eq 'BUCH' and I_VIQMEL-QMART = 'Q1'.
    CALL FUNCTION 'POPUP_TO_CONFIRM'
      EXPORTING
        TITLEBAR       = 'E-mail'
        TEXT_QUESTION = 'E-mail Göndermek istiyormusunuz ?'
      IMPORTING
        ANSWER         = answer
      EXCEPTIONS
        TEXT_NOT_FOUND = 1
        OTHERS         = 2.
if answer eq 1 and ulke = 'TR'.
lt_mailtxt ='Değerli Müşterimiz,'.
APPEND lt_mailtxt.clear lt_mailtxt.
lt_mailtxt = 'Şikayetiniz sistemimize alınmıştır. Müşteri şikayeti sorumlularımız sizlerle en yakın zamanda irtibata '.
APPEND lt_mailtxt.clear lt_mailtxt.
lt_mailtxt = 'geçeceklerdir. Şikayetiniz için teşekkür eder, saygılarımızı sunarız.'.
APPEND lt_mailtxt.clear lt_mailtxt.
lt_mailtxt =''.
APPEND lt_mailtxt.clear lt_mailtxt.
data: it_packing_list like sopcklsti1 occurs 0 with header line,
       it_receivers like somlreci1 occurs 0 with header line,
        gd_cnt type i,
        gd_sent_all(1) type c,
        gd_doc_data like sodocchgi1,
        gd_error type sy-subrc.
gd_doc_data-doc_size = it_packing_list-body_num * 255.
Populate the subject/generic message attributes.
gd_doc_data-obj_langu = sy-langu.
gd_doc_data-obj_name = 'SAPRPT'.
gd_doc_data-obj_descr = 'Naksan KGM'.
gd_doc_data-sensitivty = 'F'.
Describe the body of the message
clear it_packing_list.
refresh it_packing_list.
it_packing_list-transf_bin = space.
it_packing_list-head_start = 1.
it_packing_list-head_num = 0.
it_packing_list-body_start = 1.
describe table lt_mailtxt lines it_packing_list-body_num.
it_packing_list-doc_type = 'RAW'.
append it_packing_list.
CLEAR it_receivers.
it_receivers-receiver = email.
it_receivers-rec_type = 'U'.
it_receivers-com_type = 'INT'.
it_receivers-notif_del = 'X'.
it_receivers-notif_ndel = 'X'.
append it_receivers.
call function 'SO_DOCUMENT_SEND_API1'
       exporting
            document_data              = gd_doc_data
            put_in_outbox              = 'X'
            sender_address             = 'sinan.tataroglu@***.com'
            sender_address_type        = 'INT'
            commit_work                = 'X'
       importing
            sent_to_all                = gd_sent_all
       tables
            packing_list               = it_packing_list
            contents_txt               = lt_mailtxt[]
            receivers                  = it_receivers
       exceptions
            too_many_receivers         = 1
            document_not_sent          = 2
            document_type_not_exist    = 3
            operation_no_authorization = 4
            parameter_error            = 5
            x_error                    = 6
            enqueue_error              = 7
            others                     = 8.
IF sy-subrc EQ 0.
COMMIT WORK.
Push mail out from SAP outbox.
SUBMIT rsconn01 WITH mode = 'INT' AND RETURN.
ENDIF.
elseif ulke ne 'TR' and answer eq 1.
lt_mailtxt ='Dear Customer,'.
APPEND lt_mailtxt.clear lt_mailtxt.
lt_mailtxt = 'Your compliant has just entered to system. Customer complaint responsible will contact with you ASAP.'.
APPEND lt_mailtxt.clear lt_mailtxt.
lt_mailtxt = 'Thanks for your complaint.'.
APPEND lt_mailtxt.clear lt_mailtxt.
gd_doc_data-doc_size = it_packing_list-body_num * 255.
Populate the subject/generic message attributes
gd_doc_data-obj_langu = sy-langu.
gd_doc_data-obj_name = 'SAPRPT'.
gd_doc_data-obj_descr = 'Naksan KGM'.
gd_doc_data-sensitivty = 'F'.
Describe the body of the message
clear it_packing_list.
refresh it_packing_list.
it_packing_list-transf_bin = space.
it_packing_list-head_start = 1.
it_packing_list-head_num = 0.
it_packing_list-body_start = 1.
describe table lt_mailtxt lines it_packing_list-body_num.
it_packing_list-doc_type = 'RAW'.
append it_packing_list.
CLEAR it_receivers.
it_receivers-receiver = email.
it_receivers-rec_type = 'U'.
it_receivers-com_type = 'INT'.
it_receivers-notif_del = 'X'.
it_receivers-notif_ndel = 'X'.
append it_receivers.
call function 'SO_DOCUMENT_SEND_API1'
       exporting
            document_data              = gd_doc_data
            put_in_outbox              = 'X'
            sender_address             = 'peykan.samli@****.com'
            sender_address_type        = 'INT'
            commit_work                = 'X'
       importing
            sent_to_all                = gd_sent_all
       tables
            packing_list               = it_packing_list
            contents_txt               = lt_mailtxt[] "it_message
            receivers                  = it_receivers
       exceptions
            too_many_receivers         = 1
            document_not_sent          = 2
            document_type_not_exist    = 3
            operation_no_authorization = 4
            parameter_error            = 5
            x_error                    = 6
            enqueue_error              = 7
            others                     = 8.
IF sy-subrc EQ 0.
COMMIT WORK.
Push mail out from SAP outbox.
SUBMIT rsconn01 WITH mode = 'INT' AND RETURN.
ENDIF.

Cancelamento de NF-e parado (batch status 05, process status 02)

Bom dia pessoal,
Ontem tivemos um problema no GRC/PI de um cliente, onde por alguma razão o certificado estava sendo rejeitado. Depois de vários problemas causados por isso, foi resetado o j2ee e o sistema voltou a operar normalmente.
As sequelas disso foram duas notas para as quais foi solicitado o cancelamento, agora elas estão com status de processamento 02 (Sent to Signature Service) e batch status 05 (Result Received).
Seguindo uma orientação para um caso parecido (),
peguei os MsgIDs das mensagens dessas NFs na /xnfe/acknowledg (ambas com SIGNC), encontrei-as no SXI_MONITOR do PI, onde elas são listadas 2x cada, com os seguintes status
1 - Status = Transfer to Process Engine (, Ack. Status = branco
2 - Status = Processed Successfully, Ack. Status = Still awaiting acknowledgment (bola verde com interrogação)
Ao tentar dar restart nas mensagens, recebo a seguinte mensagem de erro:
You cannot restart XML message E07AFA5FD584CEF1B15C3C4A927627EC with this status/type
Message no. XMS_ADM085
Diagnosis
You want to reschedule an XML message that has already been processed (Restart). However, the XML message status or type does not permit a restart.
System Response
You can only restart asynchronous XML messages.
Furthermore, you can only reschedule XML messages with errors. You cannot restart correctly processed XML messages or XML messages with the status Being Processed.
Tem algo que possa ser feito sem ter que alterar tabelas?
Como a equipe responsável pelo PI/GRC fica fora do BR, é bem complicado conseguir autorização para qquer coisa nesse sentido em PRD.
ps.: Agora cliquei no "Expand all messages", para cada um dos MsgIDs, apareceram 2 novas linhas, uma com status = Scheduled (bandeira verde) e outra com status Scheduled for Outbound Processing (seta preta), ambos com o awaiting ack.
=> SMQ1 e SMQ2 ambas sem entradas.
Obrigado!
Eduardo Hartmann

Eduardo,
O NFe type = 2 (cancelamento)?
Se sim, me parece que o pedido de cancelamento foi enviado pra assinatura e nao teve resposta, provavelmente devido ao fato de o J2EE estar fora. Nesse caso, o batch status é irrelevante (ele só é relevante pro processo de envio de NFe, não pra cancelamento/inutilização).
O "correto" seria vc identificar onde a mensagem de assinatura parou (i.e. se em alguma fila - SMQ1/SMQ2, se tem q restartar o BPM etc.). Mas como o passo de assinatura é stateless, diferentemente do processamento da SEFAZ, vc poderia simplesmente "marretar" um status de erro de assinatura de cancelamento na /xnfe/nfe_hist (verifique o valor apropriado do error status no domínio do campo) e restartar a assinatura do cancelamento pelo monitor de NFe do GRC, aba de erro de assinatura.
Abs,
Henrique.

105 lote esta processando - Erro 40 de sistema de PI - Batch Status Query

Prezados,
Nós temos um lote em GRC com os detalhes seguintes código de estado - 105 lote esta processando.
Nós temos um lote em GRC com os detalhes seguintes:
- Código de estado: 105 "lote esta processando"
- Estado de lote: 04 "pedido enviou"
- Estado de Error: 40 questão de estado de lote: Erro de sistema de PI"
Reiniciando o lote por monitor de GRC resulta em um erro "Erro processo inicial Envie Lote (lote ID 000000000013825)"
Algumas ideas ou sugestoes para proceder?
Obrigado
Marc de Ruijter
Key words for thread search:
- Error status 40 Batch status query: PI system error
- Batch status 04 request sent
- Status code 105 batch being processed

Creio que estou com o mesmo problema,
Estou com um lote com erro no status 5 mensagem "Consulta de status de lote: erro de sistema PI" e ao reiniciar o lote encontro a mensagem a abaixo:
"Erro ao inicializar o processo Enviar lote (nº de lote 000000000000XXX)".
Na sxi_monitor do PI não apresenta erro nenhum!! eu conferi a tabela citada na thread e tinham vários registros e um deles referente ao meu lote. Apaguei apenas o referente ao meu lote porem ainda não reinicia.

Project Server 2010 - Change Status Manager

End Goal: We would like to perform this change via SQL statement - which I believe I have I feel like I am missing something and not sure what it is.
Background: We migrated from a different product to Project Server 2010, while our team members were assisting users to move their projects from the old application to Project 2010 they did not realize their names would appear as status
managers.
The quick solution would be to tell the owners of the projects to change the information themselves (republish or go in themselves and change every line); however we feel this can be cumbersome and too much work due to having hundreds of projects and there
are thousands of fields that need to be modified. I can quickly accomplish what I want with an UPDATE command and be done with it (no user involvement).
What I am running into in my test environment is that I can modify the fields (query below) to the appropriate status manager, but I cannot get the changes to appear in Project Professional - it still shows the old value.
I have used the following command to change the Status Manager to the Project Owner (I'm new to SQL, and we no longer have a DBA - so if my code isnt the greatest...I'll fix it)
USE ProjectServer_ReportingUPDATE MSP_EpmTaskSET TaskStatusManagerUID = MSP_EpmProject.ProjectOwnerResourceUIDFROM MSP_EpmProjectWHERE MSP_EpmTask.ProjectUID = MSP_EpmProject.ProjectUID
This modifies all the values correctly - Project Owners become the Status Manager in SQL
Question: Is there something I am missing or can do OR I am not doing to make this new value show up? Is there a better way to do this from an administrative point of view, with no customer/user interaction?
Your help is greatly appreciated
Thank You
kbwrecker

Merely my personal opinion having been a Project Server 2010 admin in a medium-sized corporation:
I think you are going to seriously do some damage if you go about trying to modify SQL tables behind Project Server's back. There are a LOT of operations that go into a simple "publish" and I doubt that the minor changes you want to make will account for
all of them. Are you confident you're adjusting all of the values necessary? You may have a detrimental impact on in-flight approvals, timesheets, projects, tasks, assignments.. There is just far too much IMO.
Believe me, I know it is not an ideal solution to have the business make their own adjustments. However sometimes it is just what has to be done. My vote is to craft brief instructions and send them out to the PMs. It's easy to do, they can change one row
and then drag the field down like in Excel to edit all the rest; it's a 1-minute operation, max.
Due to the nature of the field, (not being something you can edit via PWA, and even in Project Pro it only allows you to change it to yourself or another current Status Mgr) I think you'll have a hard time scripting this one via macro etc.. However if you
do find a way, seriously keep in mind your scope and don't edit them all at once, it will need to kick off publishes and check-ins for all the affected projects.
Good luck!

Batch status change with UD

Hi Everybody,
I have a question about batch status change while taking UD. I understand that stock posting and batch status for each UD code is decided by the value in 'Posting proposal UD' field in Selected Set settings. I understand that I can customize the movement types for the values (eg VMENGE01, VMENGE02 etc) in config. But that is only for stock posting. From what setting is the Batch status decided eg. If we approve, the batch is unrestricted and if we reject it is restricted.
Can I customize those values which are available in the drop down in the 'Posting proposal UD' ? Can I create a value of my own ?
Regards,
Manish Saraswat

Manish,
execute tcode QS51
you will be able to see 'Posting Proposal UD' in "Selected Set ". Now select that line (Posting Proposal UD line). Status for Posting Proposal UD should be "Released"
After selecting that line on left hand side there is " Dialog Structure " in that there is " Selected Set Code " Click on that.
Complete list of code will come you can add and modify those codes.
Hope now its clear to you.
Edited by: tejasg on Mar 24, 2010 4:21 PM

MHKIM:(AP) Payment Batch의 status중 Overflow에 대해서

QUESTION
=========
payment batch를 생성할때,
status - overfolw가 왜 나타나는지 확인할수 있을까요?
(APP-SQLAP-10049)
ANSWER
========
APP-SQLAP-10049 error는 Payment Batch처리시에 대상 invoice가 없으므로,
View Invoice를 눌러도 data가 보이지 않을 것이라는 것입니다.
그렇기 때문에, 해당 Payment Batch를 Confirm하게되면, 자동으로 void될 것이라는 내용입니다.
Overflow status는 대상 invoice가 없을 경우 입력되는 값입니다.
AP User Guide (5-101) 자료를 보내드립니다.
* Overflow
Complete remittance information, (for example, a list
of the invoices paid), did not fit on the actual payment document,
and Payables used an overflow payment document to record the
additional remittance information. You send to the supplier only
the remittance portion of this payment document with any other
remittance stubs and the payment. Overflow payment
documents are void.
Preliminary register report를 출력해보시면,
Payment Batch에 대한 대상 invoice는 나타나지 않을 것입니다.
Confirm작업을 하면, 자동 Void되므로,
새로운 조건으로 Payment Batch를 입력해주시기 바랍니다.

Error-IM258-This refers to an error in central status management.

Dear All
We have used the enhancement "MCI10001" for triggering the external E mail while scheduling the maintenance plan using T code IP10.
System will fetch the E mail ID from the equipment master -partner function either Vendor or User responsible and sends the mail
But while executing IP10 system throws an error message as follows
Error Msg no: IM 258- Object does not exist (Status Management)
This refers to an error in central status management.
Kindly help on the above issue
Regards
Thyagarajan
Edited by: thyagarajan krishnamurthy on Feb 18, 2011 11:10 AM
Edited by: thyagarajan krishnamurthy on Feb 18, 2011 2:28 PM

Dear,
Please refer the OSS Note 437878 - Status data missing for PM/CS notifications .
Regards,
R.Brahmankar

Batch status disappearing after taking the UD (QA11)

Hi Experts,
We are facing the following issue (ECC6.0 EHP5 with no enhancement activated):
- when the UD is made for the IL created at GR from purchase order (origin 01), the batch status initially set at GR (Q) is cleared; same time the UD for the IL is recorded and kept correctly (UD has the new status)
- when this UD is changed for the same IL, the batch status is getting updated with the new status; the UD for the IL is correctly updated, too.
We have implemented the note 1687321, but the problem still persists.
Has anyone of you faced the similar problem? Any hints where to look for the root-cause?
I've checked the user exits for batch update and QA11 (based on forum posts), but they are not called at making UD or they have correct values.
Thanks for help,
/J

Hi FF,
I think we are on the same page with terminology
Indeed, our process is a bit "enhanced" I would say. When doing the GR from purchase order, the batch characteristic LOBM_UDCODE is pre-filled with the UD of "Q" (LEANQM1 Q) whereas the IL created upon packing of HUs has no UD.
Then, when user makes UD for this IL, the pre-filled UD on batch level should be changed to the UD user made. It is not and the value disappears. I've run some checks on the ABAP code and the issue seems to be caused by the VB_CHANGE_BATCH used in the MQEVAF40 in form charge_klassifizieren. When the initial UD is made (QA11), the internal table for this f-n module has only the new values the batch classification is to be updated with. When the UD change is made (QA12) - both new and old values are provided. If I change the internal table values to include old and new ones for the initial UD, the process works correctly (batch LOBM_UDCODE is updated with new value).
As we are upgrading to ECC6 EHP5, I've compared the flow to the ECC5 and the values provided to VB_CHANGE_BATCH at initial UD (QA11) are the same for both systems. The process works in ECC5. As result, we have created the OSS message.
In MSC3n changes to the batch characteristics are visible from change docs - and the log is kept for QA11 and QA12. For the removal of LOBM_UDCODE it displays "deleted" values, and for QA12 it shows "created" values. In other words - change logs are working correctly.
Once SAP responds to OSS message I will update this tread. Any ideas appreciated.
/J

BATCH STATUS REPEATING IN GRN PLD

Dear Gurus,
I have added a field in GRN PLD for Batch status (i.e RELEASED, REJECTED, LOCKED) but when i run the pld the print layout repeats the line items in numbers of thousand even.
I want to know how can I remove this duplication.
Please guide me in this matter.
Regards
Amad Ahmed

Hi,
You can remove by editing PLD. Please share your PLD here to check.
Thanks.

Event creation with status management

Hello esteemed gurus ... it's your friendly workflow noob again
It seems once people get a sniff that there is a someone who knows a bit about workflow in the company, everyone wants a piece of you!
So... I have been asked to setup a workflow that will trigger when a user changes a user status on an SD contract. I've done some reading and I believe I'm nearly there but need a little help ...
I have setup event creation with transaction BSVZ for object category VBK, specified my status profile, and business object BUS2034 and I'm using the event "CHANGED", within this I have set a status restriction to particular status of my user status profile.
In my workflow definition I have specified the start event "CHANGED" for my business object BUS2034.
The thing is, the workflow starts for every change to the contract, whereas I was expecting it to only start when the particular status I defined in my status management was set in the contract header.
Are there any additional settings I need to make in order to restrict the starting conditions of the this workflow?
Many thanks once again.
Neil

Hi Neil,
There is two options to restrict the workflow.
First one is start condition. You can check the workflow log. If your required field is populated in the Workflow container you can use start condition to restrict the workflow. In the Basic data of workflow template, Start condition is there. You can use the condition editor to set the condition.
If your field is not populated by default, then you can use check function module for this. You need to create one FM, and in transaction swe2, the FM needs to be Configured. The concept is, based on the Sales document number you can get the required field and check the condition inside the FM. If the condition satisfied just leave it. The workflow will be triggered. If the condition is not satisfied raise a Exception. So that the Workflow will not be triggered.
Thanks,
Viji.

Batch status updating using function module BAPI_BATCH_SAVE_REPLICA

Hi,
I want to change batch status after creating the outbound delivery through inbound idoc, i was able to create delivery , but after creation, i should update the batch status using function module BAPI_BATCH_SAVE_REPLICA, but i was unable to execute this function module correctly,
Can any one provide details like what are minimum things that are required to update the batch status using this function module.
In my system batches are defined at plant level.
Please let me know the solution if any one knows this.
With regards.
P.Prasanth.

Look at BAPI_INCOMINGINVOICE_POST
Rob

Importance of batch status management.

Similar Messages

Maybe you are looking for