Batch Issue

Hello
We are having some kind of regression issue with batches here, as this was not impacting us from the R3 (execution) side we didnt notice this impact until now the impact is really from the APO side eventhough the source of this issue is from the R3 side. The issue is, the Production date and the SLED is not getting populated for the generic Batches created when the GR is done at the 3PL(Via and inbound Idocs in to SAP)Currently there is no issues with the batches at plants , the issue is only with the generic batches created by the GR at the 3PLs.When I compared for 5778 Prod date and SLED date were populated untill prod date 7/3(before upgrade) and then the dates were not populated in the batches.This is happening for all the DCs and from what I noticed to all materials.
What causes this,any way to fixed it.
Thanks
JJ

Dear sakthi,
When u post GRN wrt P.O, System picks the batch number which you have given in P.O.......automatically....just try once again...
If still u have problem, check the external number range for the Batch Number assignment..
regards,

Similar Messages

  • EDI batching issue while handling the exception.

    I am trying to batch the inbound IDOC message coming throught external release as the requirement is to batch the EDI messages
    for every IDOC having multiple BGM's. For eg if the 1st IDOC has 4 BGM's and second Idoc has 3 BGM's there should be 2 different batches
    of EDI each for 1 idoc.
    Achived this using external release trigger and delay mechanism, however if suppose the 1st Idoc fails to process in the 3rd message due to mapping
    issue then the previous 2 BGM's and already sent to the messagebox and subscribed by the batching orchestration. And when the second message is arriving
    with suppose 3 BGM's, the 2 BGM's are getting batched with them..
    For eg : 1st IDOC -  4 BGM repeating record -- 3rd is failed in orchestration looping but previous 2 are already sent to messagebox and subscribed by batching orchestration
    2nd IDOC -  with 3 BGM are processed successfully and then releasing an external trigger making the previous 2 also to get batched with the 2nd IDOC.
    My requirement is if there is any mapping issue then the previous BGM's which are sent should not get batched by the batching orchestration.
    Could anyone please suggest on the same?

    If third message fails, what do you want to do with previous messages? I think your batching orchestration should deal with incomplete batch after a period of time. You anyways won't be able to retrieve idoc second time.
    Secondly, It looks like you want to build create atomatic type of solution, for this you need to have one buffering place where you keep all successfully mapped messages intermediately. Again you need control message mechanism to notify batch complete etc.
     (Perhaps you need to explore more on batching orchestration itself).
    Another thing, if sap doesn't send single batch into multiple idocs, then you can probably create an orchestration to create whole batch and send control message to trigger edi batching.
    If this answers your question please mark it as Answer and if this post is helpful, please vote as helpful. Thanks !

  • Appworx Batch Issue - SQL ERROR CODE:-12705

    Hi Experts.
    I am facing an issue in TEST Appworx. Batches are not executing, throwing error
    “ Threads submitted - starting thread tracking (Logon) SQL ERROR CODE:-12705” for all batches.
    It is happening for all batches.
    Work around:
    1-     I thought that may be appworx is not able to make connection with DB so I created one customized batch which connect db and update table, , it completed successfully,
    2-     At DB level for Error “12705” it cause due to lang parameter; I check and found it is also currect, no issue with lang
    Please advice.
    Thanks

    Wrong forum - while many Oracle Retail users also use Appworx, this is a problem between Appworx and communication with the Oracle Database.
    Your best option is to use the UC4 support site, where they have a forum community : https://uc4.service-now.com/ (requires current support and login)

  • Sender WF-BATCH issue

    Hi All,
    I have gone through many forums but didn't find the exact solution to my problem. Actually we have configured E recruitment EHP4 but my all approvers in their SAP UWL receiving workitems from administrator instead of initiator of workflow and the same configuration is working fine in Development server and workitems come with the name of initiator .
    We have configured SWU3 also in dev server and production server but in production server it is creating this issue , pls let me know if there is some setting for changing our WF-BATCH user so that approvers receive mails from Initiator rather than administrator.
    Thanks and regards,
    Soni.

    Hi Soni,
    It can never happen that your are getting mails in DEV from initiator's ID and in PRD from WF-BATCH ID with the same settings done in both.
    To resolve your issue -
    1) If you are using SEND MAIL step type in workflow, then mails will go from WF-BATCH id only.
    2) If you are using Function Module to send the mail, then set  the sender's email id to the one as that of Initiator' id.
    3) If you are using standard report RSWUWFML2 or something, then mails will go from that ID always by using which you schedule the background job.
    Please check your settings in both the systems thoroughly in DEV as well as in PRD.
    Regards,
    Guddan

  • Batch issue were all are blanks

    Hello
    We are having some kind of regression issue with batches here, as this was not impacting us from the R3 (execution) side we didnt notice this impact until now the impact is really from the APO side eventhough the source of this issue is from the R3 side. The issue is, the Production date and the SLED is not getting populated for the generic Batches created when the GR is done at the 3PL(Via and inbound Idocs in to SAP)Currently there is no issues with the batches at plants , the issue is only with the generic batches created by the GR at the 3PLs.When I compared for 5778 Prod date and SLED date were populated untill prod date 7/3(before upgrade) and then the dates were not populated in the batches.This is happening for all the DCs and from what I noticed to all materials.
    What causes this,any way to fixed it.
    Thanks
    JJ

    The SLED dates are only calculated automatcially if a shelf life value is maintained for the plant the material is in.  If it is maintained, the system then requires a production date to be enterred at GR. 
    It could be that someone did not maintain the shelf life value for the materials in your DC's or plants during the upgrade.  If there is no real shelf life, you can enter a large value like 9999 for the field.
    Now since it sounds like your creating all these through an IDOC, then it could be in the IDOC process.  That there is missing mapping, or incorrect mapping or the data simply is not provided.  I would have no idea with regard to that as I have no clue what is being done in your system for creating the IDOC's and processing them.
    The other very remote possibilty is that when you upgraded, someone didn't set the batch level correctly in config for the new system and your being batched managed at a plant level and not at the material, (or possibly client level).  Hopefully that's not that problem cause then you really have your work cut out for you!!!
    Crag

  • Batch issue to production

    Hi...i have to issue raw material which is in batch  in my storage location with charachterstics of expiration date.
    NoW i have to issue against prodcutionorder. How and where i can see the all batch  depends on date  at the time of  issue.
    How can i make use of BATCH DETERMINATION.
    Reply get rewarded
    Thnaks

    Hi,
    i hope u done sufficicient batch mgt config.
    u need to maintain condition records in MBC1 tocde w.r.to startegy type and MT 261 combination
    check and reply
    guru

  • BizTalk Server 2010 - Batching Issue

    Hi - I have setup and configured a Party and under Batching configuration setup the Party Name, Filter as ReceivePortName and Message Type and setup schedule for testing for every 5 mins. When I am dropping the message receiving following errors :
    xlang/s engine event log entry: Uncaught exception (see the 'inner exception' below) has suspended an instance of service 'Microsoft.BizTalk.Edi.RoutingOrchestration.BatchRoutingService(49b4780c-52fe-7b25-8e71-23f6d6ba8962)'.
    The service instance will remain suspended until administratively resumed or terminated. 
    If resumed the instance will continue from its last persisted state and may re-throw the same unexpected exception.
    InstanceId: bc7e6a70-9f6c-413f-9746-18266fba7b63
    Shape name: 
    ShapeId: 00000000-0000-0000-0000-000000000000
    Exception thrown from: segment 1, progress 0
    Inner exception: Exception occurred when persisting state to the database.
    Exception type: PersistenceException
    Source: Microsoft.XLANGs.BizTalk.Engine
    Target Site: Void Commit()
    The following is a stack trace that identifies the location where the exception occured
       at Microsoft.BizTalk.XLANGs.BTXEngine.BTXXlangStore.Commit()
       at Microsoft.BizTalk.XLANGs.BTXEngine.BTXXlangStore.ScheduleComplete(Boolean terminate)
       at Microsoft.BizTalk.XLANGs.BTXEngine.BTXService.ScheduleComplete(Context ctx, Boolean finalPersisting, Boolean terminate)
       at Microsoft.XLANGs.Core.Service.Persist(Boolean dehydrate, Context ctx, Boolean idleRequired, Boolean finalPersist, Boolean bypassCommit, Boolean terminate)
       at Microsoft.XLANGs.Core.TransactionalContext.OnCommit()
       at Microsoft.XLANGs.Core.AtomicTransaction.OnCommit()
       at Microsoft.BizTalk.Edi.RoutingOrchestration.BatchRoutingService.segment1(StopConditions stopOn)
       at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s, StopConditions stopCond, Exception& exp)
    Additional error information:
            A batch item failed persistence Item-ID 69062828-e34d-42c6-8c38-bd43bee7c619 OperationType MAIO_CommitBatch Status -1061151998 ErrorInfo The published message could not be routed because no subscribers were found. .
    Exception type: PersistenceItemException
    Additional error information:
            A batch item failed persistence Item-ID bc7e6a70-9f6c-413f-9746-18266fba7b63 OperationType MAIO_InstanceComplete Status 12589892 ErrorInfo .
    Exception type: PersistenceItemException
    Additional error information:
            Failed to publish (send) a message in the batch. This is usually because there is no one expecting to receive this message.  The error was The published message could not be routed because no subscribers were found.  with
    status -1061151998.
    Exception type: PublishMessageException
    Additional error information:
            Failed to publish (send) a message in the batch. This is usually because there is no one expecting to receive this message.  The error was The published message could not be routed because no subscribers were found.  with
    status -1061151998.
    Exception type: PublishMessageException
    Additional error information:
            Failed to publish (send) a message in the batch. This is usually because there is no one expecting to receive this message.  The error was The published message could not be routed because no subscribers were found.  with
    status -1061151998.
    Exception type: PublishMessageException
    Additional error information:
            Failed to publish (send) a message in the batch. This is usually because there is no one expecting to receive this message.  The error was The published message could not be routed because no subscribers were found.  with
    status -1061151998.
    Exception type: PublishMessageException
    Additional error information:
            Failed to publish (send) a message in the batch. This is usually because there is no one expecting to receive this message.  The error was The published message could not be routed because no subscribers were found.  with
    status -1061151998.
    Exception type: PublishMessageException
    Additional error information:
            Failed to publish (send) a message in the batch. This is usually because there is no one expecting to receive this message.  The error was The published message could not be routed because no subscribers were found.  with
    status -1061151998.
    Exception type: PublishMessageException
    Additional error information:
            Failed to publish (send) a message in the batch. This is usually because there is no one expecting to receive this message.  The error was The published message could not be routed because no subscribers were found.  with
    status -1061151998.
    Exception type: PublishMessageException
    Additional error information:
            Failed to publish (send) a message in the batch. This is usually because there is no one expecting to receive this message.  The error was The published message could not be routed because no subscribers were found.  with
    status -1061151998.
    Exception type: PublishMessageException
    Additional error information:
            Failed to publish (send) a message in the batch. This is usually because there is no one expecting to receive this message.  The error was The published message could not be routed because no subscribers were found.  with
    status -1061151998.
    Exception type: PublishMessageException
    MBH

    This error can occur when the RoutingOrchestration attempts to send a message to the BatchingOrchestration and the BatchingOrchestration instance is not started.
    Ensure that the BatchingOrchestration instances are running before submitting documents to be batched.
    Known Issues with EDI Batching
    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful.

  • Hi batch issue

    Hi,
    Can anyone tell me, how to see the program name of sap batch job.
    We are having some performence issue in batch job.How it could be optimized or improved.
    Regards
    San

    RESOLVED & CLOSED

  • Batch issues in V11.3 compare to V11.1

    I am using same settings in V11.3 and V11.1, but in V11.3 pdfs are generating in different batch file compare to V11.1. Any one can help me.

    Gireesh,
    Have you reviewed your error logs to determine why those transactions are not routing correctly? I have noticed in previous upgrades (especially between 11.0 and 11.4) that there were some bugs fixed. It may be that you were previously taking advantage of the bug's output unknowingly, and when the bug was fixed, your processing doesn't function as expected. I can try to look back and find out to what specifically this is attributed.
    -- Update:
    I was able to recall the bug that was fixed. Prior versions (I'm assuming prior to 11.3) of Documaker allowed DAL script to be used in for the Data section of a field, e.g. CALL("MyDalScript"). In these prior versions, you could execute the SETFLD() method to set the value of the field calling the DAL script, and the RETURN value from the script would be ignored. This was a bug. Now, you must include the RETURN call to set the value of the field, otherwise the field will remain empty. This could be a problem if you are inspecting values of fields for batching purposes.
    Example - you have a field which maps data using CALL("MYSCRIPT"):
    BEGINSUB MYSCRIPT
    * Works in 11.0, doesn't work in 11.3+
    myValue = GetData("1,HEADER 24,10")
    SETFLD(@(),myValue)
    RETURN();
    ENDSUB
    BEGINSUB MYSCRIPT
    myValue = GetData("1,HEADER 24,10")
    RETURN(myValue);
    ENDSUB
    --Andy
    Edited by: calittle on May 3, 2010 4:45 PM

  • BATCH ISSUE UN PRODN ORDER

    Dear all,
    I have here two scenario regarding batch selection
    SCenario 1 :
    1 want to produce 5fg for which i require 5 sg & which is available in stock in 3 diffrent batches of quantity 2,2,1 respectively.
    When i create prodn order for fg & goto component overview & select sg & do batch determinatiion ,I want the system should split my required quantity automatically. how it should be done.
    2. same scenrio instead of 5fg it isr 5 sg & i require 5 rm for this which is again available in different batches of 2,2,1 respectively
    When i do batch determination system should split iy automaticaly. how it should be done

    Hi,
    Answer is already there in your question itself.
    do batch determinatiion
    Search in this forum to get help on batch determination. you will find so many useful threads.
    Regards,
    Dhaval

  • Automatic batch issue by backflush

    Sir i want to observe the effects of backflush means i want to issue material automatically without using t-code MIGO ( GI ) .Give me list of settings.
               I am online............

    Backflush indicator can be set in the material master or in Workcenter or in Routing or in Production order.
    For consuming the material you can set the default storage location in the material master itself in the MRP view or you can add in the BOM item view.
    Regards,
    Chintan

  • Batch issue problem.

    In t- code MIGO i wish that while mentioning batch no. only pending batches no. and no. of material quantities ( which is shown in t-code MMBE ) should be displayed in batch help .I am on line waiting for reply .
    Regards
    Abhi

    Hi,
    i think is not possible  if it s so then there is no meaning for batch.
    thanks,
    Mohan

  • RPM 1323 batch issue Newitemlocbatch

    I am getting below error while executing RPM newitemlocbatch batch.If you have any idea please guide me.
    I am waiting for your respond.
    Please find the below error message for your reference.
    **Exception in thread "main" java .lang.nonclassdeffoundererror: com.retek.rpm.batch.newitemlocbatch**
    Regards
    prabhat

    Check Once The jar files are available in below path.
    /home/oracle/Oracle/Middleware/user_projects/domains/JAVA_domain/retail/rpm13/rpm-batch/lib
    If there are jar files the problem is with classpath is not set to that jar files .
    Regards
    rajkumar

  • Reim Batch issue

    [oracle@retailsols reim-batch]$ ./reimpurge reim PURGE ALL COMMIT
    2012-11-21 15:58:56,215 INFO [main] oracle.retail.reim.batch.BatchRunner - Runn ing with arguments: [BatchPurgeBatch, reim, PURGE, ALL, COMMIT]
    2012-11-21 15:58:56,391 INFO [main] org.springframework.context.support.ClassPa thXmlApplicationContext - Refreshing org.springframework.context.support.ClassPa thXmlApplicationContext@65faba46: display name [org.springframework.context.supp                                                                                                 ort.ClassPathXmlApplicationContext@65faba46]; startup date [Wed Nov 21 15:58:56                                                                                                  IST 2012]; root of context hierarchy
    2012-11-21 15:58:56,616 INFO [main] org.springframework.beans.factory.xml.XmlBe anDefinitionReader - Loading XML bean definitions from class path resource [com/                                                                                                 retek/reim/reim-datasource-config.xml]
    2012-11-21 15:58:57,815 INFO [main] org.springframework.beans.factory.xml.XmlBe anDefinitionReader - Loading XML bean definitions from class path resource [com/                                                                                                 retek/reim/reim-service-config.xml]
    2012-11-21 15:59:07,325 INFO [main] org.springframework.beans.factory.xml.XmlBeanDefinitionReader - Loading XML bean definitions from class path resource [com/retek/reim/reim-dao-config.xml]
    2012-11-21 15:59:07,384 INFO [main] org.springframework.beans.factory.xml.XmlBeanDefinitionReader - Loading XML bean definitions from class path resource [com/retek/reim/reim-batch-config.xml]
    2012-11-21 15:59:07,447 INFO [main] org.springframework.beans.factory.xml.XmlBeanDefinitionReader - Loading XML bean definitions from class path resource [com/retek/reim/reim-util-config.xml]
    2012-11-21 15:59:07,547 INFO [main] org.springframework.context.support.ClassPathXmlApplicationContext - Bean factory for application context [org.springframework.context.support.ClassPathXmlApplicationContext@65faba46]: org.springframework.beans.factory.support.DefaultListableBeanFactory@f8622f3
    2012-11-21 15:59:08,390 INFO [main] org.springframework.beans.factory.config.PropertyPlaceholderConfigurer - Loading properties file from class path resource [com/retek/reim/reim.properties]
    2012-11-21 15:59:09,202 INFO [main] org.springframework.context.support.ClassPathXmlApplicationContext - Bean 'loginCredentialBean' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
    2012-11-21 15:59:09,207 INFO [main] org.springframework.context.support.ClassPathXmlApplicationContext - Bean 'org.springframework.beans.factory.config.PropertyPathFactoryBean#4f4db0e3' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
    2012-11-21 15:59:11,559 INFO [main] org.springframework.context.support.ClassPathXmlApplicationContext - Bean 'org.springframework.beans.factory.config.PropertyPathFactoryBean#4f4db0e3' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
    2012-11-21 15:59:11,561 INFO [main] org.springframework.context.support.ClassPathXmlApplicationContext - Bean 'org.springframework.beans.factory.config.PropertyPathFactoryBean#75982fc1' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
    2012-11-21 15:59:11,562 INFO [main] org.springframework.context.support.ClassPathXmlApplicationContext - Bean 'org.springframework.beans.factory.config.PropertyPathFactoryBean#75982fc1' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
    2012-11-21 15:59:11,589 INFO [main] org.springframework.context.support.ClassPathXmlApplicationContext - Bean 'dataSource' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
    2012-11-21 15:59:11,597 INFO [main] org.springframework.context.support.ClassPathXmlApplicationContext - Bean 'transactionManager' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
    2012-11-21 15:59:11,606 INFO [main] org.springframework.context.support.ClassPathXmlApplicationContext - Bean '(inner bean)' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
    2012-11-21 15:59:11,607 INFO [main] org.springframework.context.support.ClassPathXmlApplicationContext - Bean '(inner bean)' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
    2012-11-21 15:59:11,607 INFO [main] org.springframework.context.support.ClassPathXmlApplicationContext - Bean 'org.springframework.transaction.config.internalTransactionAdvisor' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
    2012-11-21 15:59:11,695 INFO [main] org.springframework.beans.factory.support.DefaultListableBeanFactory - Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@f8622f3: defining beans [org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0,loginCredentialBean,dataSource,transactionManager,org.springframework.aop.config.internalAutoProxyCreator,org.springframework.transaction.config.internalTransactionAdvisor,simpleJdbcTemplate,transactionManagerFactory,com.retek.reim.services.SupplierOptionsService#0,com.retek.reim.services.NonMerchandiseDocumentService#0,com.retek.reim.services.ItemSupplierService#0,com.retek.reim.services.matching.CreditNoteMatchStatusService#0,com.retek.reim.services.EdiRejectService#0,com.retek.reim.services.EdiDocumentService#0,com.retek.reim.services.DiscrepancyPurgeService#0,DisputedCreditMemoResolutionRollupBatch,BatchPurgeBatch,FixedDealUploadBatch,CreditNoteAutoMatchBatch,AutoMatchBatch,ReceiptWriteOffBatch,DiscrepancyPurgeBatch,FinancialPostingBatch,EdiUploadBatch,ComplexDealUploadBatch,EdiDownloadBatch,ReasonCodeActionRollupBatch,AccountWorkspacePurgeBatch,FinancialPostingWorkspacePurgeBatch,autoDiscrepancyResolutionDao,costDiscrepancyDao,complexDealDao,receiverUnitAdjustmentDao,taxCalculationDao,ediRejectDocumentDetailTaxDao,creditNoteMatchCompletionDao,costDiscrepancyHistoryDao,matchProcessDao,matchQtyVarianceHistoryDao,docDetailReasonCodesDao,stageFixedDealDao,itemSupplierDao,matchResultDao,documentTaxDao,receiptWriteOffHistoryDao,nonMerchTaxDao,documentDetailRcTaxDao,fixedDealTaxDao,parentNonMerchTaxesDao,invoiceDetailAllowanceTaxDao,resolutionActionDao,matchResultItemDao,creditNoteMatchHistoryDao,ediRejectDocumentTaxDao,financialsGLStageDao,matchResultItemHistoryDao,documentDao,ediRejectDocumentDetailDao,qtyDiscrepancyHistoryDao,matchResultHistoryDao,summaryMatchDao,accountDao,termsDao,dateTimeDao,taxDataDao,DBSequenceLoaderDao,glOptionsDao,financialPostingAccountDao,supplierBasedCreditNoteMatchCandidateDao,matchDocumentToleranceDao,shipSkuDao,supplierOptionsDao,receiptDao,invoiceDetailDao,nonMerchandiseEntryDao,ediRejectDocumentDetailAllowTaxDao,invoiceDetailTaxDao,matchCostVarianceHistoryDao,ediRejectDocumentDao,dealDynamicSegmentsDao,itemTaxAuditDao,creditNoteQtyDiscrepancyDao,financialsAPStageDao,receiptItemPostingDao,ediRejectDocumentNonMerchTaxDao,varianceDao,itemSupCountryDao,orderLocationDao,creditNoteCostDiscrepancyDao,dealDetailDao,dynamicMappingDao,matchQtyVarianceDao,partiallyMatchedReceiptDao,ediRejectDocumentNonMerchDao,documentHoldingDao,stageComplexDealDao,fixedDealDao,matchDocHistoryDao,parentNonMerchDao,matchPoolKeyConfigDao,orderDao,qtyDiscrepancyDao,taxDiscrepancyDao,documentDetailDao,matchAttemptDao,applicationUserDao,documentVatDao,ediRejectDocumentDetailAllowDao,orderItemTaxAuditDao,financialPostingDao,matchCostVarianceDao,invoiceDetailAllowanceDao,documentMatchedCreditNoteDiscrepancyWriteOffPostingService,documentMatchedReleasedCreditNotePostingService,documentPrepayInvoicePostingService,receiptWriteOffPostingService,financialPostingService,documentMatchedNonHeldCreditNotePostingService,documentApprovedCreditNotePostingService,documentCreditMemoPostingService,documentInvoicePostingService,documentMatchedUnpersistedCreditNoteVWTPostingService,documentNonMerchandisePostingService,financialPostingStagingService,documentDebitMemoPostingService,documentPrepayParentInvoicePostingService,webServiceConsumerService,taxService,ediDocumentService,receiptWriteOffHistoryService,receiptService,taxDiscrepancyService,dynamicMappingService,varianceService,receiverAdjustmentService,financialPostingAccountService,financialApplicationIntegrationService,fixedDealUploadService,dealDynamicSegmentsService,reasonCodeActionRollupService,dealService,ediRejectService,invoiceDetailService,systemOptionsService,invoiceMaintenanceService,documentDetailService,taxDiscrepancyResolutionService,termsService,vatDiscrepancyService,applicationUserService,parentInvoiceService,complexDealUploadService,documentHoldingService,varianceResolutionService,accountService,log4jLoggingService,documentService,periodService,itemSupplierService,dateTimeService,nonMerchandiseEntryService,supplierOptionsService,autoDiscrepancyResolutionService,supplierBasedAutoMatchTaskExecutionService,detailMatchService,creditNoteMatchAttemptSummaryLevelService,creditNoteMatchAttemptDetailLevelService,creditNoteAutoMatchInitService,autoMatchService,headerOnlyInvoiceTaxValidationService,matchService,summaryMatchService,matchStatusService,creditNoteVarianceService,creditNoteMatchAttemptOneToOneLevelService,creditNoteSummaryMatchService,creditNoteAutomatchService,creditNoteDetailMatchService,manualGroupUIService,quantityReviewListUIService,discrepancyResolutionUIService,priceReviewCostSelectionLoadUIService,priceReviewListUIService,logger,toStringStyleLogger,systemDate,springContext,org.springframework.context.annotation.internalRequiredAnnotationProcessor,org.springframework.context.annotation.internalAutowiredAnnotationProcessor,org.springframework.context.annotation.internalCommonAnnotationProcessor,org.springframework.context.annotation.internalPersistenceAnnotationProcessor,daoFactory,reIMSystemOptionsService,invoiceAdvSearchService,serviceFactory,discrepancyPurgeService]; root of factory hierarchy
    2012-11-21 15:59:22,528 INFO [main] oracle.retail.reim.batch.BatchProcessor - Executing BatchPurgeBatch...
    2012-11-21 15:59:24,916 ERROR [main] com.retek.reim.manager.LoginServiceImpl -
    com.retek.reim.merch.utils.ReIMException: Could not complete login.
    at com.retek.reim.manager.LoginServiceImpl.login(LoginServiceImpl.java:160)
    at com.retek.reim.batch.BatchUtils.start(BatchUtils.java:274)
    at com.retek.reim.purge.BatchPurge.main(BatchPurge.java:43)
    at oracle.retail.reim.batch.jobs.BatchPurgeBatch.performBatch(BatchPurgeBatch.java:17)
    at oracle.retail.reim.batch.ABatchProcess.execute(ABatchProcess.java:34)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:301)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
    at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
    at $Proxy21.execute(Unknown Source)
    at oracle.retail.reim.batch.BatchProcessor.executeBatch(BatchProcessor.java:41)
    at oracle.retail.reim.batch.BatchRunner.configureAndRunBatch(BatchRunner.java:65)
    at oracle.retail.reim.batch.BatchRunner.main(BatchRunner.java:26)
    Caused by: com.retek.reim.merch.utils.ReIMException: Invalid username or password.
    at com.retek.reim.manager.LoginServiceImpl.validateLocalUserUsingDatabase(LoginServiceImpl.java:178)
    at com.retek.reim.manager.LoginServiceImpl.login(LoginServiceImpl.java:155)
    ... 18 more
    2012-11-21 15:59:24,920 ERROR [main] com.retek.reim.purge.BatchPurge -
    oracle.retail.reim.batch.BatchExecutionException: com.retek.reim.merch.utils.ReIMException: Could not complete login.
    at com.retek.reim.batch.BatchUtils.start(BatchUtils.java:285)
    at com.retek.reim.purge.BatchPurge.main(BatchPurge.java:43)
    at oracle.retail.reim.batch.jobs.BatchPurgeBatch.performBatch(BatchPurgeBatch.java:17)
    at oracle.retail.reim.batch.ABatchProcess.execute(ABatchProcess.java:34)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:301)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
    at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
    at $Proxy21.execute(Unknown Source)
    at oracle.retail.reim.batch.BatchProcessor.executeBatch(BatchProcessor.java:41)
    at oracle.retail.reim.batch.BatchRunner.configureAndRunBatch(BatchRunner.java:65)
    at oracle.retail.reim.batch.BatchRunner.main(BatchRunner.java:26)
    Caused by: com.retek.reim.merch.utils.ReIMException: Could not complete login.
    at com.retek.reim.manager.LoginServiceImpl.login(LoginServiceImpl.java:160)
    at com.retek.reim.batch.BatchUtils.start(BatchUtils.java:274)
    ... 17 more
    Caused by: com.retek.reim.merch.utils.ReIMException: Invalid username or password.
    at com.retek.reim.manager.LoginServiceImpl.validateLocalUserUsingDatabase(LoginServiceImpl.java:178)
    at com.retek.reim.manager.LoginServiceImpl.login(LoginServiceImpl.java:155)
    ... 18 more
    I am getting above problem when i am running with correct user alias

    [oracle@retailsols reim-batch]$ ./reimpurge ADMIN/retek PURGE ALL COMMIT
    2012-11-27 11:20:00,237 INFO [main] oracle.retail.reim.batch.BatchRunner - Running with arguments: [BatchPurgeBatch, ADMIN/retek, PURGE, ALL, COMMIT]
    2012-11-27 11:20:00,344 INFO [main] org.springframework.context.support.ClassPathXmlApplicationContext - Refreshing org.springframework.context.support.ClassPathXmlApplicationContext@5f7a8a02: display name [org.springframework.context.support.ClassPathXmlApplicationContext@5f7a8a02]; startup date [Tue Nov 27 11:20:00 IST 2012]; root of context hierarchy
    2012-11-27 11:20:00,502 INFO [main] org.springframework.beans.factory.xml.XmlBeanDefinitionReader - Loading XML bean definitions from class path resource [com/retek/reim/reim-datasource-config.xml]
    2012-11-27 11:20:01,215 INFO [main] org.springframework.beans.factory.xml.XmlBeanDefinitionReader - Loading XML bean definitions from class path resource [com/retek/reim/reim-service-config.xml]
    2012-11-27 11:20:07,875 INFO [main] org.springframework.beans.factory.xml.XmlBeanDefinitionReader - Loading XML bean definitions from class path resource [com/retek/reim/reim-dao-config.xml]
    2012-11-27 11:20:07,984 INFO [main] org.springframework.beans.factory.xml.XmlBeanDefinitionReader - Loading XML bean definitions from class path resource [com/retek/reim/reim-batch-config.xml]
    2012-11-27 11:20:08,072 INFO [main] org.springframework.beans.factory.xml.XmlBeanDefinitionReader - Loading XML bean definitions from class path resource [com/retek/reim/reim-util-config.xml]
    2012-11-27 11:20:08,850 INFO [main] org.springframework.context.support.ClassPathXmlApplicationContext - Bean factory for application context [org.springframework.context.support.ClassPathXmlApplicationContext@5f7a8a02]: org.springframework.beans.factory.support.DefaultListableBeanFactory@a50a649
    2012-11-27 11:20:09,531 INFO [main] org.springframework.beans.factory.config.PropertyPlaceholderConfigurer - Loading properties file from class path resource [com/retek/reim/reim.properties]
    2012-11-27 11:20:10,239 INFO [main] org.springframework.context.support.ClassPathXmlApplicationContext - Bean 'loginCredentialBean' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
    2012-11-27 11:20:10,243 INFO [main] org.springframework.context.support.ClassPathXmlApplicationContext - Bean 'org.springframework.beans.factory.config.PropertyPathFactoryBean#6e84cc09' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
    2012-11-27 11:20:12,026 INFO [main] org.springframework.context.support.ClassPathXmlApplicationContext - Bean 'org.springframework.beans.factory.config.PropertyPathFactoryBean#6e84cc09' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
    2012-11-27 11:20:12,028 INFO [main] org.springframework.context.support.ClassPathXmlApplicationContext - Bean 'org.springframework.beans.factory.config.PropertyPathFactoryBean#506f9b8e' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
    2012-11-27 11:20:12,029 INFO [main] org.springframework.context.support.ClassPathXmlApplicationContext - Bean 'org.springframework.beans.factory.config.PropertyPathFactoryBean#506f9b8e' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
    2012-11-27 11:20:12,049 INFO [main] org.springframework.context.support.ClassPathXmlApplicationContext - Bean 'dataSource' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
    2012-11-27 11:20:12,051 INFO [main] org.springframework.context.support.ClassPathXmlApplicationContext - Bean 'transactionManager' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
    2012-11-27 11:20:12,060 INFO [main] org.springframework.context.support.ClassPathXmlApplicationContext - Bean '(inner bean)' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
    2012-11-27 11:20:12,061 INFO [main] org.springframework.context.support.ClassPathXmlApplicationContext - Bean '(inner bean)' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
    2012-11-27 11:20:12,061 INFO [main] org.springframework.context.support.ClassPathXmlApplicationContext - Bean 'org.springframework.transaction.config.internalTransactionAdvisor' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
    2012-11-27 11:20:12,149 INFO [main] org.springframework.beans.factory.support.DefaultListableBeanFactory - Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@a50a649: defining beans [org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0,loginCredentialBean,dataSource,transactionManager,org.springframework.aop.config.internalAutoProxyCreator,org.springframework.transaction.config.internalTransactionAdvisor,simpleJdbcTemplate,transactionManagerFactory,com.retek.reim.services.SupplierOptionsService#0,com.retek.reim.services.NonMerchandiseDocumentService#0,com.retek.reim.services.ItemSupplierService#0,com.retek.reim.services.matching.CreditNoteMatchStatusService#0,com.retek.reim.services.EdiRejectService#0,com.retek.reim.services.EdiDocumentService#0,com.retek.reim.services.DiscrepancyPurgeService#0,DisputedCreditMemoResolutionRollupBatch,BatchPurgeBatch,FixedDealUploadBatch,CreditNoteAutoMatchBatch,AutoMatchBatch,ReceiptWriteOffBatch,DiscrepancyPurgeBatch,FinancialPostingBatch,EdiUploadBatch,ComplexDealUploadBatch,EdiDownloadBatch,ReasonCodeActionRollupBatch,AccountWorkspacePurgeBatch,FinancialPostingWorkspacePurgeBatch,autoDiscrepancyResolutionDao,costDiscrepancyDao,complexDealDao,receiverUnitAdjustmentDao,taxCalculationDao,ediRejectDocumentDetailTaxDao,creditNoteMatchCompletionDao,costDiscrepancyHistoryDao,matchProcessDao,matchQtyVarianceHistoryDao,docDetailReasonCodesDao,stageFixedDealDao,itemSupplierDao,matchResultDao,documentTaxDao,receiptWriteOffHistoryDao,nonMerchTaxDao,documentDetailRcTaxDao,fixedDealTaxDao,parentNonMerchTaxesDao,invoiceDetailAllowanceTaxDao,resolutionActionDao,matchResultItemDao,creditNoteMatchHistoryDao,ediRejectDocumentTaxDao,financialsGLStageDao,matchResultItemHistoryDao,documentDao,ediRejectDocumentDetailDao,qtyDiscrepancyHistoryDao,matchResultHistoryDao,summaryMatchDao,accountDao,termsDao,dateTimeDao,taxDataDao,DBSequenceLoaderDao,glOptionsDao,financialPostingAccountDao,supplierBasedCreditNoteMatchCandidateDao,matchDocumentToleranceDao,shipSkuDao,supplierOptionsDao,receiptDao,invoiceDetailDao,nonMerchandiseEntryDao,ediRejectDocumentDetailAllowTaxDao,invoiceDetailTaxDao,matchCostVarianceHistoryDao,ediRejectDocumentDao,dealDynamicSegmentsDao,itemTaxAuditDao,creditNoteQtyDiscrepancyDao,financialsAPStageDao,receiptItemPostingDao,ediRejectDocumentNonMerchTaxDao,varianceDao,itemSupCountryDao,orderLocationDao,creditNoteCostDiscrepancyDao,dealDetailDao,dynamicMappingDao,matchQtyVarianceDao,partiallyMatchedReceiptDao,ediRejectDocumentNonMerchDao,documentHoldingDao,stageComplexDealDao,fixedDealDao,matchDocHistoryDao,parentNonMerchDao,matchPoolKeyConfigDao,orderDao,qtyDiscrepancyDao,taxDiscrepancyDao,documentDetailDao,matchAttemptDao,applicationUserDao,documentVatDao,ediRejectDocumentDetailAllowDao,orderItemTaxAuditDao,financialPostingDao,matchCostVarianceDao,invoiceDetailAllowanceDao,documentMatchedCreditNoteDiscrepancyWriteOffPostingService,documentMatchedReleasedCreditNotePostingService,documentPrepayInvoicePostingService,receiptWriteOffPostingService,financialPostingService,documentMatchedNonHeldCreditNotePostingService,documentApprovedCreditNotePostingService,documentCreditMemoPostingService,documentInvoicePostingService,documentMatchedUnpersistedCreditNoteVWTPostingService,documentNonMerchandisePostingService,financialPostingStagingService,documentDebitMemoPostingService,documentPrepayParentInvoicePostingService,webServiceConsumerService,taxService,ediDocumentService,receiptWriteOffHistoryService,receiptService,taxDiscrepancyService,dynamicMappingService,varianceService,receiverAdjustmentService,financialPostingAccountService,financialApplicationIntegrationService,fixedDealUploadService,dealDynamicSegmentsService,reasonCodeActionRollupService,dealService,ediRejectService,invoiceDetailService,systemOptionsService,invoiceMaintenanceService,documentDetailService,taxDiscrepancyResolutionService,termsService,vatDiscrepancyService,applicationUserService,parentInvoiceService,complexDealUploadService,documentHoldingService,varianceResolutionService,accountService,log4jLoggingService,documentService,periodService,itemSupplierService,dateTimeService,nonMerchandiseEntryService,supplierOptionsService,autoDiscrepancyResolutionService,supplierBasedAutoMatchTaskExecutionService,detailMatchService,creditNoteMatchAttemptSummaryLevelService,creditNoteMatchAttemptDetailLevelService,creditNoteAutoMatchInitService,autoMatchService,headerOnlyInvoiceTaxValidationService,matchService,summaryMatchService,matchStatusService,creditNoteVarianceService,creditNoteMatchAttemptOneToOneLevelService,creditNoteSummaryMatchService,creditNoteAutomatchService,creditNoteDetailMatchService,manualGroupUIService,quantityReviewListUIService,discrepancyResolutionUIService,priceReviewCostSelectionLoadUIService,priceReviewListUIService,logger,toStringStyleLogger,systemDate,springContext,org.springframework.context.annotation.internalRequiredAnnotationProcessor,org.springframework.context.annotation.internalAutowiredAnnotationProcessor,org.springframework.context.annotation.internalCommonAnnotationProcessor,org.springframework.context.annotation.internalPersistenceAnnotationProcessor,daoFactory,reIMSystemOptionsService,invoiceAdvSearchService,serviceFactory,discrepancyPurgeService]; root of factory hierarchy
    2012-11-27 11:20:24,188 INFO [main] oracle.retail.reim.batch.BatchProcessor - Executing BatchPurgeBatch...
    2012-11-27 11:20:29,123 ERROR [main] com.oracle.retail.integration.common.security.credential.CredentialStoreManager - The credential doesn't exist for the given key/userNameAlias(ADMIN/RETEK).
    2012-11-27 11:20:29,125 ERROR [main] com.oracle.retail.integration.common.security.credential.CredentialStoreManager - Unable to obtain the userName for the given key/userNameAlias(ADMIN/RETEK).
    java.lang.IllegalArgumentException: The credential doesn't exist for the given key/userNameAlias(ADMIN/RETEK).
    at com.oracle.retail.integration.common.security.credential.CredentialStoreManager.getUserName(CredentialStoreManager.java:886)
    at oracle.retail.reim.utils.CredentialStoreAccessor.getUserName(CredentialStoreAccessor.java:44)
    at com.retek.reim.batch.BatchUtils.start(BatchUtils.java:269)
    at com.retek.reim.purge.BatchPurge.main(BatchPurge.java:43)
    at oracle.retail.reim.batch.jobs.BatchPurgeBatch.performBatch(BatchPurgeBatch.java:17)
    at oracle.retail.reim.batch.ABatchProcess.execute(ABatchProcess.java:34)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:301)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
    at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
    at $Proxy21.execute(Unknown Source)
    at oracle.retail.reim.batch.BatchProcessor.executeBatch(BatchProcessor.java:41)
    at oracle.retail.reim.batch.BatchRunner.configureAndRunBatch(BatchRunner.java:65)
    at oracle.retail.reim.batch.BatchRunner.main(BatchRunner.java:26)
    2012-11-27 11:20:29,127 ERROR [main] com.retek.reim.purge.BatchPurge -
    oracle.retail.reim.batch.BatchExecutionException: java.lang.RuntimeException: Unable to obtain the userName for the given key/userNameAlias(ADMIN/RETEK).
    at com.retek.reim.batch.BatchUtils.start(BatchUtils.java:285)
    at com.retek.reim.purge.BatchPurge.main(BatchPurge.java:43)
    at oracle.retail.reim.batch.jobs.BatchPurgeBatch.performBatch(BatchPurgeBatch.java:17)
    at oracle.retail.reim.batch.ABatchProcess.execute(ABatchProcess.java:34)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:301)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
    at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
    at $Proxy21.execute(Unknown Source)
    at oracle.retail.reim.batch.BatchProcessor.executeBatch(BatchProcessor.java:41)
    at oracle.retail.reim.batch.BatchRunner.configureAndRunBatch(BatchRunner.java:65)
    at oracle.retail.reim.batch.BatchRunner.main(BatchRunner.java:26)
    Caused by: java.lang.RuntimeException: Unable to obtain the userName for the given key/userNameAlias(ADMIN/RETEK).
    at com.oracle.retail.integration.common.security.credential.CredentialStoreManager.getUserName(CredentialStoreManager.java:903)
    at oracle.retail.reim.utils.CredentialStoreAccessor.getUserName(CredentialStoreAccessor.java:44)
    at com.retek.reim.batch.BatchUtils.start(BatchUtils.java:269)
    ... 17 more
    Caused by: java.lang.IllegalArgumentException: The credential doesn't exist for the given key/userNameAlias(ADMIN/RETEK).
    at com.oracle.retail.integration.common.security.credential.CredentialStoreManager.getUserName(CredentialStoreManager.java:886)
    ... 19 more
    Done
    Execution time (seconds) = 0.011
    2012-11-27 11:20:29,133 ERROR [main] com.retek.reim.purge.BatchPurge - Aborted in init.
    2012-11-27 11:20:29,137 INFO [main] oracle.retail.reim.batch.BatchProcessor - Batch completed, status: FAILED_INIT (1).
    2012-11-27 11:20:29,138 INFO [main] oracle.retail.reim.batch.BatchRunner - FAILED_INIT (1) returned from batch process.
    I am getting the above problem even though i used alias-name or username/pwd can you please help me.
    Regards
    Rajkumar
    Edited by: 972448 on Nov 26, 2012 9:42 PM

  • Good Issue batch Flows at GR for finish good Material

    Hi Gurus,
    Please Help me on below scenarios
    1)Good issue material batch and its characteristic automatically flows to Finish Good Material at the time of Good receipt of Process order.
    2) If Component of Finish Material ie Good issue material is having the different batches issued to the Finish material Process order then System should only consider those batch which is having the Characteristic values is having more that 50%
    Exam : Good Issue material X and requirement qty 10
    Then Component issue 10 qty with 2 batches  A and B
    Batch A  Qty 5 : Char              Value          Batch B Qty 5       Char      Value
                               Density            10                                             Density     15
    Tthen Finished Good batch consider only batch B which is having the maximum density.
    Here we want the same batch B and it should automacticaly flows  to the Finish product at the time of GR ( Process order )
    I tried with Batch derivation but we want the same Good issue batch to finished material
    Please help me on this scanrios and if we are going for development then how it is possible technically ( with Functioan specification)
    Regards,
    Saurabh

    Hi Gurus,
    Please look above the scenario and reply.
    Regards,
    Saurabh

Maybe you are looking for