Sending IDOC while creating a transport order (WM)

Hi,
I'm looking for the customizing options which let me configure that an (WMTOID) IDOC is generated while creating an transport order based on a transport request... Transaction for this is LT04
Thanks a lot.
Kind regards
Markus

You will need to setup output definition for tranport order.  User transaction NACE to setup outbound EDI type message.  Also you will need to setup Port and partner profile settings.
Mahesh

Similar Messages

  • Mapping datas from idoc while creating a sales order.

    Hi Friends,
    From the idoc i want to fill the field 'YOUR REFERNCE' in the tag ORDER DATA at header level while creating a sales order. From which segment i can find the datas for that field.
    Your answers will be valuable.
    Thanks,
    Bestin
    Edited by: Be$t!N on Aug 26, 2009 4:41 PM

    Hi,
    You can find the Your Reference field in the segment E1EDKA1 and the field name is IHREZ.  This Your reference field is at the Partner level. This is a standard field.
    If you can let me know at which place you want this field to be populated then we can find another suitable field in the IDOC.
    Thanks,
    Mahesh.

  • Screen shots for creating Stock transport order

    hi,
    Can anyone send me the screen shots for creating Stock transport order between plants within company code?
    Regards,
    Swathi

    hi
    pls refer to HELP.SAP.COM INTHIS SELECT BEST PRACTISES and in that select building blocks it will ask country wise select india and give ur req type of industry .here u can see J05 AS materials management also other req  i mean  sto and all u can configure
    regards
    srinivas kona

  • Error while creating a Planned Order

    Hi SAP Experts,
    I have an error encountered while creating a Planned Order which is "Mode linkage problem with mode number".
    Diagnosis:
        An application program called an LCA routine and the following error occurred:
        An order has at least one condition with mode linkage with the same mode number. The activities of this condition must have compatible modes. The modes are compatible when each mode of one activity has a mode for the other activity with the same mode number. The first activity that violates the condition is given in the return code table in ABAP.
    Please enlighthen me what is this error and what should be done to this error.
    Thanks in advance,
    Raymond

    Check the PPM or PDS being used in the Planned Order.
    Most likely you have a Setup Activity followed by Produce Activity. However the Mode (i.e. Resource) used in the two activities are different. The same Mode needs to be used both in Setup and corresponding Produce activity.
    Hope this helps,
    somnath

  • Error while creating a new order on deployed cartridge

    hello all
    I have deployed "bb_ocm_demo" sample cartridge on the weblogic.
    but while creating a new order, i am getting error as below.
    An OMS Exception has been thrown. Reason: com.mslv.oms.OMSException: (Wrapped) com.mslv.oms.handler.order.cache.c
    com.mslv.oms.OMSException: (Wrapped) com.mslv.oms.handler.order.cache.c
         at com.mslv.oms.jsp.processor.RequestProcessorSupport.processRequest(Unknown Source)
         at com.mslv.oms.jsp.processor.RequestProcessorSupport.processRequest(Unknown Source)
         at com.mslv.oms.jsp.processor.RequestProcessorSupport.a(Unknown Source)
         at com.mslv.oms.jsp.processor.RequestProcessorSupport.a(Unknown Source)
         at com.mslv.oms.jsp.processor.CreateNewOrderProcessor.processRequest(Unknown Source)
         at com.mslv.oms.jsp.controller.RequestController.a(Unknown Source)
         at com.mslv.oms.jsp.controller.RequestController.processRequest(Unknown Source)
         at com.mslv.oms.jsp.controller.MainServlet.a(Unknown Source)
         at com.mslv.oms.jsp.controller.MainServlet.doProcess(Unknown Source)
         at com.mslv.oms.jsp.controller.MainServlet.doPost(Unknown Source)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
         at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
         at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:22)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
    Caused By: (Wrapped) java.io.NotSerializableException: com.mslv.oms.handler.order.cache.c
         at com.tangosol.util.ExternalizableHelper.toBinary(ExternalizableHelper.java:215)
         at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache$ConverterValueToBinary.convert(PartitionedCache.CDB:3)
         at com.tangosol.util.ConverterCollections$ConverterMap.put(ConverterCollections.java:1674)
         at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache$ViewMap.put(PartitionedCache.CDB:1)
         at com.tangosol.coherence.component.util.SafeNamedCache.put(SafeNamedCache.CDB:1)
         at com.mslv.oms.handler.order.cache.AbstractOrderCacheManager.a(Unknown Source)
         at com.mslv.oms.handler.order.cache.AbstractOrderCacheManager.a(Unknown Source)
         at com.mslv.oms.handler.order.cache.AbstractOrderCacheManager.a(Unknown Source)
         at com.mslv.oms.handler.order.cache.AbstractOrderCacheManager.a(Unknown Source)
         at com.mslv.oms.handler.order.cache.AbstractOrderCacheManager.getOrderHistoryCacheNode(Unknown Source)
         at com.mslv.oms.handler.order.cache.AbstractOrderCacheManager.getOrderHistoryCacheNode(Unknown Source)
         at com.mslv.oms.handler.order.cache.AbstractOrderCacheManager.checkMaxInstancesExceeded(Unknown Source)
         at com.mslv.oms.handler.order.f.a(Unknown Source)
         at com.mslv.oms.handler.createorder.CreateOrderHandlerEJB.process(Unknown Source)
         at com.mslv.oms.handler.a.processRequest(Unknown Source)
         at com.mslv.oms.jsp.processor.RequestProcessorSupport.a(Unknown Source)
         at com.mslv.oms.jsp.processor.RequestProcessorSupport.processRequest(Unknown Source)
         at com.mslv.oms.jsp.processor.RequestProcessorSupport.processRequest(Unknown Source)
         at com.mslv.oms.jsp.processor.RequestProcessorSupport.a(Unknown Source)
         at com.mslv.oms.jsp.processor.RequestProcessorSupport.a(Unknown Source)
         at com.mslv.oms.jsp.processor.CreateNewOrderProcessor.processRequest(Unknown Source)
         at com.mslv.oms.jsp.controller.RequestController.a(Unknown Source)
         at com.mslv.oms.jsp.controller.RequestController.processRequest(Unknown Source)
         at com.mslv.oms.jsp.controller.MainServlet.a(Unknown Source)
         at com.mslv.oms.jsp.controller.MainServlet.doProcess(Unknown Source)
         at com.mslv.oms.jsp.controller.MainServlet.doPost(Unknown Source)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
         at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
         at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:22)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
    Caused By: java.io.NotSerializableException: com.mslv.oms.handler.order.cache.c
         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1164)
         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330)
         at com.tangosol.util.ExternalizableHelper.writeSerializable(ExternalizableHelper.java:2253)
         at com.tangosol.util.ExternalizableHelper.writeObjectInternal(ExternalizableHelper.java:2697)
         at com.tangosol.util.ExternalizableHelper.serializeInternal(ExternalizableHelper.java:2601)
         at com.tangosol.util.ExternalizableHelper.toBinary(ExternalizableHelper.java:211)
         at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache$ConverterValueToBinary.convert(PartitionedCache.CDB:3)
         at com.tangosol.util.ConverterCollections$ConverterMap.put(ConverterCollections.java:1674)
         at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache$ViewMap.put(PartitionedCache.CDB:1)
         at com.tangosol.coherence.component.util.SafeNamedCache.put(SafeNamedCache.CDB:1)
         at com.mslv.oms.handler.order.cache.AbstractOrderCacheManager.a(Unknown Source)
         at com.mslv.oms.handler.order.cache.AbstractOrderCacheManager.a(Unknown Source)
         at com.mslv.oms.handler.order.cache.AbstractOrderCacheManager.a(Unknown Source)
         at com.mslv.oms.handler.order.cache.AbstractOrderCacheManager.a(Unknown Source)
         at com.mslv.oms.handler.order.cache.AbstractOrderCacheManager.getOrderHistoryCacheNode(Unknown Source)
         at com.mslv.oms.handler.order.cache.AbstractOrderCacheManager.getOrderHistoryCacheNode(Unknown Source)
         at com.mslv.oms.handler.order.cache.AbstractOrderCacheManager.checkMaxInstancesExceeded(Unknown Source)
         at com.mslv.oms.handler.order.f.a(Unknown Source)
         at com.mslv.oms.handler.createorder.CreateOrderHandlerEJB.process(Unknown Source)
         at com.mslv.oms.handler.a.processRequest(Unknown Source)
         at com.mslv.oms.jsp.processor.RequestProcessorSupport.a(Unknown Source)
         at com.mslv.oms.jsp.processor.RequestProcessorSupport.processRequest(Unknown Source)
         at com.mslv.oms.jsp.processor.RequestProcessorSupport.processRequest(Unknown Source)
         at com.mslv.oms.jsp.processor.RequestProcessorSupport.a(Unknown Source)
         at com.mslv.oms.jsp.processor.RequestProcessorSupport.a(Unknown Source)
         at com.mslv.oms.jsp.processor.CreateNewOrderProcessor.processRequest(Unknown Source)
         at com.mslv.oms.jsp.controller.RequestController.a(Unknown Source)
         at com.mslv.oms.jsp.controller.RequestController.processRequest(Unknown Source)
         at com.mslv.oms.jsp.controller.MainServlet.a(Unknown Source)
         at com.mslv.oms.jsp.controller.MainServlet.doProcess(Unknown Source)
         at com.mslv.oms.jsp.controller.MainServlet.doPost(Unknown Source)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
         at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
         at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:22)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
    please provide a solution or cause.

    It seems like a problem with the Coherence cache configuration for your installation.
    Is your installation clustered?
    Is the problem specific to this cartridge (i.e. do orders from other cartridges work well in this environment)?
    Suggest you log a problem with Oracle Support and/or try the problem in a different environment.
    Regards,
    Brian.

  • Error while creating a process order

    Dear Guru's
    While creating a process order ,i am facing an error.
    "Unable to create batch. Storage location BPSS is invalid for material 112100050
    Message no. 40116".
    How to assign specific storage loaction to that particular material.I have assigned in material master "work scheduling tab",But it was throwing an error while doing process order.Pls help me to solve this problem.
    Thanks in advance,
    Rgds,
    cherukuri

    Hi Cherukuri
    Are u using special procurement key "80"? It seems that storage location is not mentioned for the header material in the production plant.
    Maintain this using T Code MMSC. It will solve ur issue
    Rgds

  • While creating the Transfer Order system is not picking Sale order stock?

    Hi All,
    In the B2B  process the system is not picking the stock from from sale order stock while creating the transfer order? Please suggest.
    Summary : Here we are creating the PR in the sale order and STO is created using the same PR to procure the materials from the WM plant to sale order plant. Since here intialy we are moving the stock to our sale order in WM plant and then picking the same. But while creating the Transfer order system is not picking the sale order stock in WM plant.
    Regards.

    C S Javali
    Check in schedule line in transaction flow whether Transfer Req /assembly is checked or not
    Regards
    Pradeep

  • Error while creating manual planned order in apo

    Dear expert
    While I am creating manual planned order i am getting error as message /sapapo/rrp251
    Every thing is correct BOM and PV's no error after consistency check and it getting succesfully transffered to APO and it is also visible in APO
    But while creating manual planned orders planned order are not getting generated  I am using BLock planning with PPDS
    Please help How to resolve it
    Regards
    Virender

    Hi
    The error message /SAPAPO/RRP251 - Error occurred while creating order means While creating an order, the system encountered problems, such as, for example, no available components or components that are available late, orders that could not be scheduled, and so on.
    I think system attempted to solve the availability problems by using alternative procurement options. This was not successful. The order could not be created. Check the exceptional situations in the planning protocol, under Goto -> Planning log, and deal with the causes of the exceptional situations if this is possible or necessary.
    Thanks
    Amol

  • Error while creating a Purchase Order

    Hi Friends,
    I am new to SAP MM. I am getting a problem while creating a purchase order. I created Purchase Info Record, Source List, but while creating Purchase Order, price is not picking from the purchase order. I am getting an error i.e. Net Value must be greater than 0. I checked all the settings, but getting same error.
    Could you please solve this

    Hi,
    Give some price at the item level for the item in the PO.
    And check the Pricing procedure in PO
    Hope it helps you.
    Thanks.

  • Getting error 'Item 00000 does not exist' while creating a salse order

    Hi All,
    We are facing an issue, we get an error message saying 'Item 00000 does not exist' while creating a sales order for a particular order type, we do not get this problem with all the materials, only a few of them and the materials which give a problem are part of the supersession chain. The problem is not even coming for all the superseded materials.
    This problem is occuring with none of the other order types but just one. We have compared the configuration for the order types for which this error is not coming and the order type which is giving the problem, and its exactly the same.
    When creating the sales order through VA01 even though the error message comes, but on hitting the enter button the processing goes further. But when creating the sales order through the background program the processing stops the moment the error message comes and the Sales Order does not get created.
    Your valuable suggestions for helping us resolving this issue will be highly appreciated.
    Regards,
    Geeta

    HI Geeta
    As per your post "Problem is when you are executing VA01 in background sales orders are not generating due to error message".
    Apart from configuration check alternative is "Take ABAPer's help and change this error message type to warning/information message type in the system". With warning/information message type you could be able to create sales orders in background also.
    try and revert

  • Material Listing Error while creating the sales order

    Hi Guru's
    I have mantained a material in the lisitng for A002 combiantion for SO/DC/Pric. ref. material
    While creating the sales order is throwing an error as material is not listed so the transaction is not possible.
    I have done the basic invetingation on the folowing aspects
    1)checking the material in the listing
    2)Validity periods
    3)Material not blcoked
    4)Mateial is extened for the respective sales org
    Kindly help ASAP.
    Thanks & Regards
    Tarakaram

    Dear SAP SD 007
    I can confidently tell that an enhancement or an user exit has been applied in your scenario
    You have to check that
    Normally when creating a sales order with respect or referring billing documents the qty will be in editable mode and it is standard problem
    Your people has solved the standard problem by enhancement
    Usually OR--LF-PGI----F2 (SAY THE QTY IS 25 UNITS)
    Now you are creating returns order with reference to F2 in the return order type Re there is a standard issue that user can edit the qty to 30 from the original 25
    To solve this only your people have used userexit
    Line items and qty greyed out means definately there is some enhancement or user exit applied
    You have to check that
    Regards
    Raja

  • Serial number error while creating the production order

    Hello frds,
    I am getting the following error while creating the production order.
    "Item 000000 requires exactly 100 serial numbers for the asset".
    If i give 100 serial numbers in the order, the error is solved. But i do not want to assign 100 serial numbers, i want to assign only 2 numbers.
    I have tried using the new serial number profile also, but it is giving same error.
    Kindly guide.
    Regards,
    Narendra Bora

    Dear Narendra
    Select the serial number profile and go to serialization procedure and set the ser. usage status 02 - Optional as below.
    Procd Procedure description Ser.Usage
    PPRL PP order release 02
    since the serail number creation is optional for order relase this will allow you to relase with out error and with serail number assigned in partial.
    Regards
    Soundar

  • Error while creating the sales order with billing reference

    hi alll
    i am getting error while creating the sales order with billing reference.The line items are coming in grey.I am not able to change the items as well as the quantity field.Can u guide me
    cheers
    shalsa007........

    Dear SAP SD 007
    I can confidently tell that an enhancement or an user exit has been applied in your scenario
    You have to check that
    Normally when creating a sales order with respect or referring billing documents the qty will be in editable mode and it is standard problem
    Your people has solved the standard problem by enhancement
    Usually OR--LF-PGI----F2 (SAY THE QTY IS 25 UNITS)
    Now you are creating returns order with reference to F2 in the return order type Re there is a standard issue that user can edit the qty to 30 from the original 25
    To solve this only your people have used userexit
    Line items and qty greyed out means definately there is some enhancement or user exit applied
    You have to check that
    Regards
    Raja

  • GOS while creating a Purchase order

    Hi,
    I have a requirement to attach documents in item level while creating a purchase order ME21N. I know that we can have GOS functionality available but, only after document is created.
    Is there a alternative solution for this?
    Thanks in advance

    Hi,
    Give some price at the item level for the item in the PO.
    And check the Pricing procedure in PO
    Hope it helps you.
    Thanks.

  • User id while  creating a purchase order

    Hello all,
    I would like to know whether there is any option to enter the user id or user name while creating a purchase order. If so could anyone post on how to do that.
    Thanks,
    Maxx

    If you are creating PO in foreground, you dont have the option of giving user id.
    But if you create POs in background using a scheduled job, then when you are scheduling the job, you can overwrite the default user id and give the user id you want. In this case all the POs created by the job, will have the user id created by you.
    But if you have to create a PO through background job, you have to give the inputs to PO through some programs may be BDCs or LSMW.
    Reward if this helps. you

Maybe you are looking for