Stock transfer Draft cannot be printed

Hello
We are using PL16 and want to print stock transfer drafts (under Inventory)
However the print funtion is not working because it is not activated.
Do you know how can we print this document?
It is odd, because other drafts (sales order,...) can be printed.
Thank you.

When opening the drafts screen, single click on the draft document (inventory transfer in this instance) just to highlight it, and then print preview / printer dialog will become activated. It prints that way.

Similar Messages

  • Closing a Stock Transfer draft (using Delphi 7)

    Hi, I have this code to close a Stock Transfer draft (ie. using 'Cancel' method):
               with GetBusinessObject(param_type) as IDocuments do begin
                 ok := GetByKey(StrToInt64(param_key));
                 if ok then result := Cancel();
            end;
    Somehow that code gives me an error. By using GetLastErrorDescription(), the error message is:
    "[Microsoft][SQL Native Client][SQL Server]Cannot insert the value NULL into column 'DocEntry', table 'SAP_TEST.dbo.DRF6'; column does not allow nulls. INSERT fails."
    FYI I used this code to close other document drafts (Sales Order Draft, Return Order Draft), and they are all OK, so looks like something is a bit different with Stock Transfer draft.
    Anybody has any idea what's wrong, and how to fix/handle it?
    Thanks.

    Hi,
    Stock Transfer and some other inventory transaction tables share the same structure with other marketing document tables. However, because the general design of the table structure is focus on marketing document part, Stock Transfer transaction will have certain limitations. You need to try more methods to close it.
    Thanks,
    Gordon

  • How can we print the Stock Transfer Purchase Order

    Hi,
    How can we print the Stock Transfer Purchase Order??
    Because from Transaction ME9L & ME9F, we can print simple PO's like NB, MPR etc..but Stock Transfer PO could not print.
    Plz guide, from where we can do it...

    Messages for PO are set in MN04. For details on how to follow this link:
    Re: Problem with PO output determination MN04
    Once the record is set here you will see the records in ME23n under messages button in header.
    Edited by: Afshad Irani on Apr 30, 2010 10:09 AM

  • MM - Stock Transfer Requirement

    Hi Gurus,
    Is there by any chance a way to use Purchasing Info Record with Stock Transfer Requirement and Stock Transfer Order.
    I need to use the "minimum purchase quantity" so that my Stock Transfer Order cannot be created below a certain amount of units...
    If we cannot use Purchasing Info Record... Does anyone have an idea  on how to set up that process ?
    Thanks in advance !
    Remi

    Thank you for your help. The only thing is that is generates Purchase Requisitions for 5 units instead of 2 units.
    I would like the system to generate a Purchase Requisition when the accumulated needs for this material are 5 units.
    Regards,
    Remi

  • Stock transfer on fixed transfer price.

    Hi,
    My client is having one requirement at the time of transfer the stock from one plant to another plant
    Supplying plant transfer the stock to receiving plant on fixed transfer price of that month not on the basis of moving avarage price.
    Is it possible in SAP with 641/101 route or not.
    Before transfer
    MAP of supplying plant       100                                                 stock qty  1
    Transfer price of month       120
    Receiving plant MAP          105                 stock qty 1
    After Transfer
    MAP of supplying plant       100                                                 stock qty  0
    Transfer price of month       120
    Receiving plant MAP         (110+120)/2 = 115               stock qty 2
    Please do the needful.
    Regards,
    Dinesh Singhal

    hi,
    During stock transfer you cannot change the price control(If it is MAP (or) Standard) with the current price only STO can be made.
    You can use 641 movement also
    G.Ganesh Kumar

  • While Printing Stock Transfer PO giving error message " Tax code in procedu

    Dear SAP MM Cons,
    I want see the print preview of stock transfer purchase order but i getting following error.
    Tax code in procedure TAXINN is invalid
    Where we need not require to give any tax code in the stock transfer PO. Can any body help me to see the printpreview of STO.
    Reagrds
    Abhishek Tiwari

    Kedarji
    Thank you.Urgent please.
    Regards
    venkat
    Edited by: garapati on Feb 15, 2008 12:06 PM

  • How tell when a draft stock transfer has been transferred to stock transfer

    Hi
    A colleague has asked if I can delete all stock transfers which have been used, ie transferred to actual stock transfers in B1 8.81
    I can delete the draft fine but I can't tell if it's been used
    There is a field called transferred in the odrf file but that always seems to be set to N
    Also the usual base document of the new stock transfer seem to be blank
    Can anyone help me please ?
    Thanks
    Regards Andy

    Hi Andy,
    You could of course just write and save an except query. Something like this:
    SELECT T0.[CardCode], T1.[ItemCode] FROM ODRF T0  INNER JOIN DRF1 T1 ON T0.DocEntry = T1.DocEntry WHERE T0.[DocNum] ='1137512'
    EXCEPT
    SELECT T0.[CardCode], T1.[ItemCode] FROM ORDR T0  INNER JOIN RDR1 T1 ON T0.DocEntry = T1.DocEntry
    This won't work in the client though. You would have to use sql server management or something
    Good luck,
    Johan
    Edited by: Johan Hakkesteegt on Feb 9, 2012 1:45 PM

  • PRINTING STOCK TRANSFER NOTE

    Hi MM Gurus,
        Please let me know the settings required to print the Stock Transfer note,
        Transaction code MB1B.
    Regards
    Yoga

    Hi Ramki,
            I have maintained the settings given by you. Still printing is not happening.
            Kindly let me know whether any additional setting is required.
    Regards
    Yoga

  • Stock Transfer Slip Print

    Hi MM Brains,
    I am transferring stock storage location to storage location (311) by using MB26 against reservation. After completion of stock transfer I want print the stock transfer details.
    But I am doing some setting in NACE, but it is not working.
    Please guide me how to do.
    Thanks in Advance,
    S.Babusingh

    Have you selected immediate print parameter in the output?
    Also you have to maintain in SU03 user relevant data I guess NDT(check in the tcode) so that system immediately trigger the output during material document creation.
    Also check the document in MIGO tcode there is check box in header, select that whether output is getting triggered or not.
    This will help to know that the output which you have created is working properly or not during manual select.
    Check and revert.

  • My printer will not recognize greeting card stock and I cannot use card programs.

    I have changed all of the necessary thing when loading card stock into the printer, and yet the printer asks for paper.  It doesn't recognize the card stock and I cannot use any of my greeting card programs.

    You are not alone with this issue. I wish that HP would accept the fact that printing with card stock is an issue that needs to be addressed and corrected. My Officejet 8600 Plus will not pick up nor print any weight (67 or 110) card stock. It is listed in their specifications that it will! Neither Best Buy or Office Depot could get their display units to print card stock either. Under troubleshooting they list a series of steps that do not apply to the basic problem. When trying to print to card stock you receive a "Out of Paper" error message. It is a known issue and not being addressed. I just posted this same problem so will see what comes back and stay in touch.

  • Cannot create copy of Std inspection type 08 (Stock transfer inspection)

    Dear All:
    I have created a copy of std inspection type 08 as Z08CP. I have made all the relevant assigments in IMG such as Maintain Inspection Lot Origins and Assign Inspection Types, Default values, etc.
    During my unit testing I did use the newly created Z08CP but I have noticed I keep getting the error message " Change the inspection stock of material XXXXX in QM only" BUT THE MOMENT I SWITCHED THE MATERIALS MASTER BACK TO inspection type 08 the problem is gone. Only when I have the std inspection type in the material master I am allow it to post a MB1b (322) and created the inpscetion lot in the background
    Weird !!
    Any ideas.
    Regards,
    Mauricio

    Let me see if i understand exactly what you guys are saying.
    Following entries have been made in IMG
    1. Plant dependent QM settings. Inspection Type for Available Stock in Quality Inspection field is empty
    2. Maintain Inspection types: Created Z08CP as copy of 08
    3. Maintain Inspection Lot Origins and Assign Inspection Types. For lot origin 08. created the following relationship
    Lot Origin 08
    01     08     Stock transfer inspection
    02     Z08CP     Prod Defect: Stock transfer inspection
    4. Default values for inspection type. Copied default values from 08 to Z08CP
    Note i did not make any changes to IMG section "Inspection for Goods Movements"
    I tried again and same error was displayed. what is that I am missing here?
    Regards,

  • Re : Inter company stock transfer through EDI

    Hi
          How to do the intercompany stock transfer through EDI. In this if Purchase order is created from one comapny a sales order should created automaticall in another Company. Fot this what is the SPRO settings.
    How to do this.
    Thanks
    Anto

    Hi,
    continues from here,
    Inbound file:     edi_in
    Function module:     See text below.
    Status file parameters
    Directory:     /home/edi/<portname>/
    Outbound file:     status.idoc
    Function module:     Leave blank if using above
    u2022     Both the portname and the exchange directory should be created according to the same naming convention. However, the portname should be in upper case whereas the corresponding directory name should be in lower case (see examples below).
         Portname (upper case):
                             <portname>
         Exchange directory name (lower case):           
                             /home/edi/<portname>
         where <portname> consists of:
         EDI<system name><client number><id char>
         <system name> is the name of  system on which port exists eg.      F01, PG1 etc.;
         <client number> is name of client on system which will use this      port; and
         <id char> is a single alphabetical character such as u2018au2019,u2019bu2019 etc.      typically,      u2018au2019 will denote dynamic outbound file naming (used      for testing) whereas      u2018bu2019 will denote static outbound file naming.      All ports will use static       inbound filenames.
    For example, the name of a port using dynamic file naming on system F01, client 610 would be named EDIF01610A.  The exchange directory would be named edif01610a. Similarly, the name of port using static file naming on system PG1, client 600 would be EDIPG1600B. The exchange directory name would be edipg1600b.
    Note that the function u201CEDI_PATH_CREATE_USERNAME_DT_TMu201D  can be used in the u201CFunction moduleu201D field  of the Outbound file parameters if IDocs are to be written to multiple files. In this case, the corresponding outbound filename field should be left blank. The standard IDoc exchange interface between the SAP EDI component and the EDI subsystem uses a single file for each transfer direction. However, should the exchange interface change, or for testing purposes, the function modules for dynamic naming can be used.
    2.4.2.     Control of EDI processes in R/3
    2.4.2.1.      Maintain: Outbound Process Code (WE41)
    IMGCross-Application ComponentsALE Extensions  Outbound
    Check that the outbound EDI processes in the R/3 system are defined.  Indicates which ABAP/4 function module to execute in order to create an outbound IDoc.
    The following assignments are available for R/3:
    2.4.2.2.      Maintain: Inbound Process Code (WE42)
    IMGCross-Application Components  ALE  Extensions  Inbound
    Check that the inbound EDI processes in the R/3 system are defined.  Indicates what kind of inbound processing to execute.
         A long list of options is available under Processing by function module, relevant ones are:
    INVF     INVOIC FI     Invoice receipt (Financial Accounting)
    INVM     INVOIC MM     Invoice verification (Mat Management)
    ORDC     ORDCHG     Change customer order
    ORDE     ORDERS     Create customer order
    ORDR     ORDRSP     Purchase order confirmation
    2.4.2.3.      Control: System Process Codes (WE40)
         Choose Processing by task.  Check that the codes indicating the type of EDI processing error are defined.  The only valid entries are the entries shown on the screen, as they are directly called via the EDI basis module.
    2.4.2.4.      Control: Status maintenance (WE47)
         Check that the codes indicating status of IDoc processing are defined.  The status values for outbound IDocs are between 01 and 39, while the status values for inbound IDocs begin with 50.  These values are delivered by SAP and cannot be customised.
    2.4.2.5.      Control: Partner Types (WE44)
         Check that the codes that identify the commercial relationships between the receiver and sender are defined.  Values are delivered by SAP.  Names of the programs and routines that validates the entry of the EDI trading partner ID:
    Partner type     Report name     Form routine
    B - Bank     RFETESTP     READ_T012
    KU - customer     RSETESTP     READ_KNA1
    LI - vendors     RSETESTP     READ_LFA1
    LS - logical system ( ALE)     RSETESTP     LOGSYS
    2.4.2.6.      Control: Forward Inbound (WE45)
    Allows for the forwarding of IDocs to a specific application.  Contains the exactly defined destination of an inbound IDoc within the SAP system.  Usually no changes are required.
    2.4.2.7.      Control: Status Process code (WE56)
    Choose Processing by task: The following set-up has been provided as default:
    Process code:     EDIS
    Identification:     TS30000078
    Description:     EDI-IDoc  status record processing
    The process code is for inbound status, The ID type is an identification code for inbound processing method (workflow or standard task) of the status record.
    3.     MM IMG CONFIGURATION
    3.1.     Global settings (IMG):
    3.1.1.     Units of measure (IMG  Global settings):
    The ISO code is important for EDI.  It is used to convert the internal SAP units of measure into standard units.
    The MM configurer must link the Unit Of Measure, EACH, with the ISO code PCE (Piece).
    3.2.     Link Schema to Purchase order
    Check the following:
    IMG  MM  Purchasing  Message determination  Message determination  Message Schemas
    Execute transaction u201CDefine Message Schemas for Purchase Orderu201D
    Select  transaction: Assign Schema to purchase order
    Add:      Usage =B for output
         Application = EF for purchase order
         Procedure = RMBEF1 for purchase order
    3.3.     Link application to EDI interface via message control:
    IMG  MM  Purchasing  Messages  Output Control
    Check following under Output Control:
         Condition table
         Access sequence
         Message types
         Message schema
         Output control
    3.4.     Enabling Multiple Output for Purchase Orders (Optional)
    For example: EDI & Printing
    IMG  MM  Purchasing  Message determination  Message determination Access sequence
    u2022     Create new access sequence (e.g. ZPUR), copy the access sequence 0001 but leaving the ''E'' flag blank (Exclusive is off). (Transaction M/50)
    u2022     Goto Define message types  maintain message types:
         Create a new message type (e.g. NEU1), setting the output type to 1 for printed output and using ZPUR as access sequence. (Transaction M/34)
    u2022     Goto Message Schema  define message schema  maintain output determination procedure:
         Update procedure RMBEF1 by adding a step for the new condition type (e.g. NEU1) prior to the standard delivered step for NEU. (Transaction M/36)
    u2022     Goto Processing program  Define Processing program  Output program: Purchase Order.
         - Add a NEU1 record to table TNAPR.  The program FORM Routine and layout must be specified.  (Copy an existing NEU record). (Transaction OMTB)
    u2022     Goto Processing program  Define Processing program  Output by partner type.
         - Add NEU1 record for VN (vendor). (Transaction OMTG)
    3.5.     Link Output type (fax=2, E-mail=7) to NEU (Purchasing)
    IMG  MM  Purchasing  Message determination  Message determination Access sequence
    u2022     Goto Processing program  Define Processing program  Output program: Purchase Order.
         - Add another NEU record to table TNAPR with the appropriate output medium. Copy an existing NEU record. (Transaction OMTB)
    u2022     Goto Processing program  Define Processing program  Output by partner type.
         - Add NEU record for VN (vendor). (Transaction OMTG)
    4.     SD APPLICATION REQUIREMENTS
    Assumption: SD is only used for testing purposes and configuration is based on a need basis - only configure the minimum.
    Reference SAP Course manual Chapter 11.
    4.1.     EDI Configurations
    4.1.1.     Conversion of SAP item categories to IDOC item categories (VOE1)
    IMG  S&D  EDI  EDI Messages  Conversion of SAP item categories to IDOC item categories
    Add the following entry:
    For Standard Item description :     0     OR     LDN
    Typically error message: ''Transaction LDN is not defined".
    4.1.2.     Partner functions
    IMG  S&D  EDI  EDI Messages  Configure EDI Partners Partner  Application  Partner function
    Check that the following partner functions exist: (at least)
    SP     Sold-to party
    VN     Vendor
    BP     Bill-to party
    SH     Ship-to party
    Note - the German abbreviation is passed to the IDoc.
    4.2.     S&D Sales Configurations
    4.2.1.     Maintain Item categories
    IMG  S&D  Sales  Sales document  Sales doc item  Define item categories
    Add LDN for standard item:
              Item type = B
              Relev for billing = B
              Tick following:     Bus data item
                                  Sched line allowed
                                  Credit active
                                  Pricing
              Screen seq. grp = N
    4.2.2.     Assign Item categories
    IMG  S&D  Sales  Sales document  Sales doc item  Assign item categories
    Add/Update the following entries:
         1     2     3
    Sales doc type     OR     OR     OR
    Item category group     NORM     DIEN     LEIS
    Item category     LDN     TAD
    LDN     LDN
    4.2.3.     Assign Schedule line categories
    IMG  S&D  Sales  Sales document  Schedule lines  Assign Schedule line categories
    Add Item category LDN to table (with no other parameters).
    4.3.     S&D Pricing Configurations
    4.3.1.     EDI pricing condition types
    IMG  S&D  Basic functions  Pricing  Pricing control  Define condition types  Maintain condition types
    Maintain the following condition types:
         EDI 1 - Calculate type =C for Quantity
         EDI 2 - Calculate type = B for Fixed amount
    4.3.2.     SD Pricing procedures (V/08)
    IMG  S&D  Basic functions  Pricing  Pricing control  Define & Assign pricing procedures
    Maintain pricing procedure for ZVAA01 (Standard). 
    Select control and add EDI1 and EDI2  as steps 1 and 5 respectively with no other parameters.
    5.     INVOICE IMG CONFIGURATION
    No additional IMG configuration (not partner specific) was needed for Inbound Invoice processing.
    Thanks,
    Swamy H P

  • Error in Stock Transfer

    Dear All,
             When i am creating STO, upto Excise invoice(JEX)  process is ok. STO-Repl. DEl.-Billing - Excis Invoice.
             But when in another plant at the time of goods recipt(MIGO) with reference to Excis Invoice(JEX) it shows the error of Base Value, it shows the message that base value for that material is not maintained.All the value BED,Ecess,Hr.Ecess are call in migo wrt to invoice but base value is zero and it appears in gray field & because of this Goods receipt cannot be done.
            Plz send some Solution for this problem.
            Award pts for useful answer.
    Thx & Regards,
    Pankaj

    Assuming you are transferring from one plant to another in same company code. So the delivery type is NL.
    1. Your base value is coming as 0 because while you are creating PO your can see your net value is coming as 0 beside quantity as 1 EA (Page 1) and this is correct because in stock transfer you need not to charge other plant as they booth are in same company code only excise need to be issued.
    2. Page 5. I can see an error as values for condition type JEXP, JCEP and JA1S are not accumulating in net instead they are going into TAX. But they should be accumulated into NET and not in TAX. Just for your info Excise duty are considered as discount and surcharge and not as TAX. You can correct it by going to condition type and change its class as A instead of D.
    3. For error message as maintain vendor for the excise invoice you need to maintain in J1ID and you problem will be solved.
    4. For error message base value as 0. You follow below steps to solve your problem.
    a. Goto IMG> Logistics – General> Tax on Goods Movements> India> Tools> Message Control.
    b. Execute and make new entry as
    4F 121 ____ _____ Warning.
    This will solve your problem.
    Regards/ashu

  • Error in stock transfer order

    Hi everyone,
    When I am doing MIGO ,In stock transfer order ,I am getting the following error,
    "Excise Invoice cannot be captured for RG1(Finished Goods) material".
    What should I do?
    Regards
    Prabudh

    Hi Prabudh,
    Can you come again with more details ?
    Are you doing STO from Manufacturing plant to selling Plant (Depot) ?
    Regards,
    Gaurav Raghav.

  • Stock Transfer B/W Two Plants ( 303 & 305 )

    Hi MM Experts.....
    Im working with the scenario of two plant stock transfer ie., 303 & 305 and in need to control the posting date of 305 should be gerater or equal to the reference document ie., 303.
    There is a field LFBNR - Document No. of Reference Document but i cannot find the reference doc number ie., 303 on that.
    Im tried to figure out the reference document in the MKPF & MSEG table but i couldn't only for 303 & 305 document alone.
    Please suggest me ......
    Regards
    MM-L.Senthil Kumar

    There is no link between 303 and 305.
    One moves stock from a storage location  into in-transit, while the other posts from in-transit to a storage location.
    Depending on the time one needs to transport the material physically, you can have stock of several movements done with 303 in in-transit.
    Further you are looking for a way to restrict posting with an earlier receipt date than issue date, but this just assumes that the GR folks are working wrong, while the people who perform the goods issue are doing everything right.
    You better analyse your process and talk with the receivers why they enter a earlier date. I doupt that they are doing this to mess around. I would even guess they are doing it because they received the goods at this earlier date, but could not perform the GR because the goods issue folks had not done their job.

Maybe you are looking for