Purchase Order Driver Program

Hi all
Am using the Standard Smartform /SAPDII/SPP_ORDER  for my purchase order rather than the script MEDRUCK.Now please tell me what is the driver program i need to submit for /SAPDII/SPP_ORDER in NACE.Please Help
Vijay

hii
  pls chk this in TNAPR table.
thanks
Edited by: pardeep kumar on Aug 11, 2008 3:26 PM

Similar Messages

  • Assigning customised purchase order driver program and form ?

    Hi ,
    I have a created my own driver program  and form form for purchase order.........after developing where should i assign it..
    i tried in nace but im getting the following error :
    Processing routine ENTRY_NEU in program ZSK_PO does not exist.
    wats the error i have made ?
    thanks,
    Siva.

    Hi
    You have to attach in the NACE itself. Check IF your program is activated and did you use:
    Form ENTRY_NEU.
    "all your code should be here.
    ENdform.
    IN your program??
    Regards,
    VIshwa.
    Edited by: Vishwa Sri Hari on Oct 22, 2008 4:18 PM

  • Purchase order driver program and configuration for nace

    i have copied the medruck in script and i need to write the driver program for that and need to configure to nace can any one tell me how to do this.

    Hi Rocky,
    Below are steps to configure:
    1. Go to transaction NACE
    2. Select EF application, click on output types
    3. Select Output type NEU and double click on processing routines
    4. Here you can give ur driver program name and script name
    Hope it will solve the problem.
    Regards
    Krishnendu

  • Purchase Order Driver Program Not loading SMARTFORM

    Hi,
    I have developed Z smartform by copying from standard form and tried to call from standard program only but here I am not able to call my Z smartform and I am able to call only Z SAPSCRIPT from this standard program.
    I have done all the necessary changes in NACE transaction but then also only when I keep the script name its working fine but when I replace this by smartform name the driver program is not calling smartform .!! why?
    Please do let me know why is it like this?
    Thanks
    Sudharshan

    Hi,
    PO driver program is written to support only SAPSCRIPT. So if you want to assign smartform in NACE, you should take a Zcopy of the driver program SAPFM06P with its include FM06PE02 as ZFM06PE02. And give the zprogram against the driver program field in NACE.
    Then you need to replace the entry_nue subroutine in ZFM06PE02 with the below code.
    form entry_neu using ent_retco ent_screen.
      data: l_druvo like t166k-druvo,
            l_nast  like nast,
            l_from_memory,
            l_doc   type meein_purchase_doc_print.
    * Data Declaration for PO smartform Modification
    DATA: fname TYPE rs38l_fnam,
            xkomk TYPE TABLE OF komk,
            gs_output TYPE ssfcompop,
            gs_dialog TYPE ssfctrlop.
      clear ent_retco.
      if nast-aende eq space.
        l_druvo = '1'.
      else.
        l_druvo = '2'.
      endif.
      call function 'ME_READ_PO_FOR_PRINTING'
           exporting
                ix_nast        = nast
                ix_screen      = ent_screen
           importing
                ex_retco       = ent_retco
                ex_nast        = l_nast
                doc            = l_doc
           changing
                cx_druvo       = l_druvo
                cx_from_memory = l_from_memory.
      check ent_retco eq 0.
       IF tnapr-sform NE ' '.
        CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
          EXPORTING
            formname           = tnapr-sform
          IMPORTING
            fm_name            = fname
          EXCEPTIONS
            no_form            = 1
            no_function_module = 2
            OTHERS             = 3.
        IF sy-subrc EQ 0.
            gs_dialog-no_dialog = 'X'.
            gs_dialog-preview = 'X'.
            gs_output-tddest = 'LP01'.
            gs_output-tdnoprev = ' '.
            gs_output-tdnoprint = ' '.
            gs_output-tdimmed = 'X'.
            gs_output-tdnewid = 'X'.
         CALL FUNCTION fname  " modify the interface as per your needs
            EXPORTING
              control_parameters = gs_dialog
              output_options     = gs_output
              user_settings      = ' '
              zxekko             = l_doc-xekko
              zxpekko            = l_doc-xpekko
            TABLES
              l_xekpo            = l_doc-xekpo
              l_xekpa            = l_doc-xekpa
              l_xpekpo           = l_doc-xpekpo
              l_xeket            = l_doc-xeket
              l_xtkomv           = l_doc-xtkomv
              l_xekkn            = l_doc-xekkn
              l_xekek            = l_doc-xekek
              l_xkomk            = xkomk
            EXCEPTIONS
              formatting_error   = 1
              internal_error     = 2
              send_error         = 3
              user_canceled      = 4
              OTHERS             = 5.
        ELSE.
          CALL FUNCTION 'ME_PRINT_PO'
            EXPORTING
              ix_nast        = l_nast
              ix_druvo       = l_druvo
              doc            = l_doc
              ix_screen      = ent_screen
              ix_from_memory = l_from_memory
              ix_toa_dara    = toa_dara
              ix_arc_params  = arc_params
              ix_fonam       = tnapr-fonam                      "HW 214570
            IMPORTING
              ex_retco       = ent_retco.
        ENDIF.
      ELSE.
        CALL FUNCTION 'ME_PRINT_PO'
          EXPORTING
            ix_nast        = l_nast
            ix_druvo       = l_druvo
            doc            = l_doc
            ix_screen      = ent_screen
            ix_from_memory = l_from_memory
            ix_toa_dara    = toa_dara
            ix_arc_params  = arc_params
            ix_fonam       = tnapr-fonam                        "HW 214570
          IMPORTING
            ex_retco       = ent_retco.
      ENDIF.
    endform.
    While calling the smartform modify the fm interface to your needs.
    This will solve your problem.
    Regards
    Karthik D

  • Purchase Order History Program - not working properly

    Dear friends
    i am developing purchase order history program in ALV,
    which shows the report of purchase order status
    i.e (fields as below).
    document no
    PO date
    line item
    material number
    material name
    purchase org
    plant
    purchase group
    orderd quantity
    ordered amount
    delivered quantity
    delivered amount
    to be delivered quantity
    to be delivered amount
    invoice quantity
    invoice amount
    to be invoiced quantity
    to be invoiced amount
    how to test from me23n
    open me23n
    enter PO number
    press status tab
    you can get some fields for verification..
    the problem is
    i can get all the details correctly except delivered amount and to be delivered amount
    it works fine in both ( material purchase order and service purchase order )
    sometimes i am getting incorrect values in service purchase order specifically in delivered amount and to be delivered amount
    why i am getting these incorrect values ??
    only couple of POs generate these things.
    i am getting these values from EKBE table and using proper filtration like movement type and etc...
    if anyone can resolve ... would be appreciable
    avirat.

    Hi,
    for getting proper Po History you need to select PO's details from EKKO table and
    Header details from CHANGEDOCUMENT_READ_HEADERS based on the details got from this FM pass
    to the FM CHANGEDOCUMENT_READ_POSITIONS and get proper details.
    This is the logic used by the standard program also to get the PO History.
    Hope this helps.
    Regards
    Bikas

  • Error While submitting Import Standard Purchase Order Concurrent Program

    Hello All,
    When I am trying to submit Import Standard Purchase Order Concurrent Program from front end, it gets submitted properly.
    and from backend,I am getting Following error.
    To get the log messages for PDOI, please use the following id to query against FND_LOG_MESSAGES table:
    AUDSID = 27810853
    ORA-01403: no data found in Package po.plsql.PO_PDOI_PVT. Procedure init_sys_parameters.0
    ORA-01403: no data found in Package po.plsql.PO_PDOI_PVT. Procedure init_startup_values.10
    ORA-01403: no data found in Package po.plsql.PO_PDOI_PVT. Procedure start_process.50
    User-Defined Exception in Package po.plsql.PO_PDOI_Concurrent. Procedure POXPDOI.30
    When I looked in Parameters in both program(manually submitted and called from backend) I found a difference.
    difference is Parameter Operating Unit. It not get submitted while program calling from backend.
    Please anybody tell me solution for this. for setting this parameter.
    (Also I have applied for patch 13001705 as per Metalink suggested).
    Thanks in advance.
    Regards
    Ravi Raj.
    Edited by: Ravi Raj on Jan 23, 2013 10:50 PM

    Please paste the code here.. there may be some parameter issue while submission.

  • Purchase order print program error

    hi experts!
    am facing a problem in my purchase order print program. the problem is that when i am trying to see the print preview the following dump error is throughing, which am not able to understand.
    the P.O total amount should be change into words( like one million then thousand thirty three kuwait dinars)
    but the total amount is not converting into as mentioned, instead the dump is encountered.
    please give me solution,
    thnaks
    *DUMP*
    Runtime Errors         CONVT_NO_NUMBER                                                             
    Exception                CX_SY_CONVERSION_NO_NUMBER                                                  
    Date and Time          05.05.2008 19:04:43                                                         
    Short text                                                                               
    Unable to interpret "1760,778.71 " as a number.                                               
    What happened?                                                                               
    Error in the ABAP Application Program                                                                               
    The current ABAP program "ZMM_SUBROUTINES" had to be terminated because it has                
        come across a statement that unfortunately cannot be executed.                                
    What can you do?                                                                               
    Note down which actions and inputs caused the error.                                                                               
    To process the problem further, contact you SAP system                                        
        administrator.                                                                               
    Using Transaction ST22 for ABAP Dump Analysis, you can look                                   
        at and manage termination messages, and you can also                                          
        keep them for a long time.                                                                    
    Error analysis                                                                               
    An exception occurred that is explained in detail below.                                      
        The exception, which is assigned to class 'CX_SY_CONVERSION_NO_NUMBER', was not               
         caught in                                                                               
    procedure "GET_AMT_IN_WORDS" "(FORM)", nor was it propagated by a RAISING                     
         clause.                                                                               
    Since the caller of the procedure could not have anticipated that the                         
        exception would occur, the current program is terminated.                                     
        The reason for the exception is:                                                              
        The program attempted to interpret the value "1760,778.71 " as a number, but                  
        since the value contravenes the rules for correct number formats,                             
        this was not possible.                                                                        
    How to correct the error                                                                               
    Whole numbers are represented in ABAP as a sequence of numbers, possibly                      
         with an algebraic sign.                                                                      
        The following are the possibilities for the representation of floating                        
        point numbers:                                                                               
    [algebraic sign][mantissa]E[algebraic sign][exponent]                                       
          [algebraic sign][whole number part].[fraction part]                                         
        For example, -12E+34, +12E-34, 12E34, 12.34                                                   
        If the error occurred in your own ABAP program or in an SAP                                   
        program you modified, try to remove the error.                                                                               
    If the error occures in a non-modified SAP program, you may be able to                        
        find an interim solution in an SAP Note.                                                      
        If you have access to SAP Notes, carry out a search with the following                        
        keywords:                                                                               
    "CONVT_NO_NUMBER" "CX_SY_CONVERSION_NO_NUMBER"                                                
        "ZMM_SUBROUTINES" or "ZMM_SUBROUTINES"                                                        
        "GET_AMT_IN_WORDS"                                                                               
    If you cannot solve the problem yourself and want to send an error                            
        notification to SAP, include the following information:                                                                               
    1. The description of the current problem (short dump)                                                                               
    To save the description, choose "System->List->Save->Local File                            
        (Unconverted)".                                                                               
    2. Corresponding system log                                                                               
    Display the system log by calling transaction SM21.                                        
           Restrict the time interval to 10 minutes before and five minutes                           
        after the short dump. Then choose "System->List->Save->Local File                             
        (Unconverted)".                                                                               
    3. If the problem occurs in a problem of your own or a modified SAP                           
        program: The source code of the program                                                       
           In the editor, choose "Utilities->More                                                     
        Utilities->Upload/Download->Download".                                                                               
    4. Details about the conditions under which the error occurred or which                       
        actions and input led to the error.                                                                               
    The exception must either be prevented, caught within proedure                                
        "GET_AMT_IN_WORDS" "(FORM)", or its possible occurrence must be declared in the               
        RAISING clause of the procedure.                                                              
        To prevent the exception, note the following:                                                 
    System environment                                                                               
    SAP-Release 700                                                                               
    Application server... "EHPAP1"                                                                
        Network address...... "10.100.150.103"                                                        
        Operating system..... "AIX"                                                                   
        Release.............. "5.3"                                                                   
        Hardware type........ "00C3B3F04C00"                                                          
        Character length.... 16 Bits                                                                  
        Pointer length....... 64 Bits                                                                 
        Work process number.. 1                                                                       
        Shortdump setting.... "full"                                                                               
    Database server... "EHPDB"                                                                    
        Database type..... "DB6"                                                                      
        Database name..... "EHP"                                                                      
        Database user ID.. "SAPEHP"                                                                               
    Char.set.... "C"                                                                               
    SAP kernel....... 700                                                                         
        created (date)... "Mar 19 2007 20:40:49"                                                      
        create on........ "AIX 2 5 005DD9CD4C00"                                                      
        Database version. "DB6_81 "                                                                               
    Patch level. 102                                                                               
    Patch text.. " "                                                                               
    Database............. "DB6 08.02., DB6 09."                                                 
        SAP database version. 700                                                                     
        Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5"                                                                               
    Memory consumption                                                                               
    Roll.... 16192                                                                               
    EM...... 29328936                                                                               
    Heap.... 0                                                                               
    Page.... 1359872                                                                               
    MM Used. 19180992                                                                               
    MM Free. 1764848                                                                               
    User and Transaction                                                                               
    Client.............. 400                                                                      
        User................ "FADISULAIMAN"                                                           
        Language key........ "E"                                                                      
        Transaction......... "ME22N "                                                                 
        Program............. "ZMM_SUBROUTINES"                                                        
        Screen.............. "SAPLMEGUI 0014"                                                         
        Screen line......... 22                                                                       
    Information on where terminated                                                                   
        Termination occurred in the ABAP program "ZMM_SUBROUTINES" - in                               
         "GET_AMT_IN_WORDS".                                                                               
    The main program was "RM_MEPO_GUI ".                                                                               
    In the source code you have the termination point in line 398                                 
        of the (Include) program "ZMM_SUBROUTINES".                                                   
        The termination is caused because exception "CX_SY_CONVERSION_NO_NUMBER"                      
         occurred in                                                                               
    procedure "GET_AMT_IN_WORDS" "(FORM)", but it was neither handled locally nor                 
         declared                                                                               
    in the RAISING clause of its signature.                                                                               
    The procedure is in program "ZMM_SUBROUTINES "; its source code begins in line                
        358 of the (Include program "ZMM_SUBROUTINES ".                                               
    Source Code Extract                                                                               
    Line  SourceCde                                                                               
    368   DATA: lt_spell LIKE spell.                                                                
      369                                                                               
    370   READ TABLE in_tab WITH KEY 'CURR'.                                                        
      371   IF sy-subrc = 0.                                                                          
      372     lf_curr = in_tab-value.                                                                 
      373   ENDIF.                                                                               
    374                                                                               
    375   READ TABLE in_tab WITH KEY 'NETWR'.                                                       
      376   IF sy-subrc = 0.                                                                          
      377     lf_netpr_01 = in_tab-value.                                                             
      378     REPLACE ',' IN lf_netpr_01 WITH ' '.                                                    
      379     CONDENSE lf_netpr_01 NO-GAPS.                                                           
      380                                                                               
    381     IF lf_curr = 'KWD'.                                                                     
      382       lf_netpr_kwd = lf_netpr_01.                                                           
      383                                                                               
    384       CALL FUNCTION 'SPELL_AMOUNT'                                                          
      385         EXPORTING                                                                           
      386           amount    = lf_netpr_kwd                                                          
      387           currency  = lf_curr                                                               
      388           filler    = ''                                                                    
      389           language  = sy-langu                                                              
      390         IMPORTING                                                                           
      391           in_words  = lt_spell                                                              
      392         EXCEPTIONS                                                                          
      393           not_found = 1                                                                     
      394           too_large = 2                                                                     
      395           OTHERS    = 3.                                                                    
      396                                                                               
    397     ELSE.                                                                               
    >>>>>       lf_netpr = lf_netpr_01.                                                               
      399       CALL FUNCTION 'SPELL_AMOUNT'                                                          
      400         EXPORTING                                                                           
      401           amount    = lf_netpr                                                              
      402           currency  = lf_curr                                                               
      403           filler    = ''                                                                    
      404           language  = sy-langu                                                              
      405         IMPORTING                                                                           
      406           in_words  = lt_spell                                                              
      407         EXCEPTIONS                                                                          
      408           not_found = 1                                                                     
      409           too_large = 2                                                                     
      410           OTHERS    = 3.                                                                    
      411     ENDIF.                                                                               
    412     IF sy-subrc <> 0.                                                                       
      413 *          MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO                                
      414 *          WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.                                        
      415                                                                               
    416     ELSE.                                                                               
    417                                                                               
    Contents of system fields                                                                         
    Name     Val.                                                                               
    SY-SUBRC 0                                                                               
    SY-INDEX 17                                                                               
    SY-TABIX 1                                                                               
    SY-DBCNT 18                                                                               
    SY-FDPOS 1                                                                               
    SY-LSIND 0                                                                               
    SY-PAGNO 0                                                                               
    SY-LINNO 1                                                                               
    SY-COLNO 1                                                                               
    SY-PFKEY NORMAL                                                                               
    SY-UCOMM PREVOUTPUT                                                                               
    SY-TITLE Held Imp. Pur. O r - ESG 5000000021 Created by Fadi Sulaiman                             
    SY-MSGTY A                                                                               
    SY-MSGID TD                                                                               
    SY-MSGNO 426                                                                               
    SY-MSGV1 NEXTPAGE                                                                               
    SY-MSGV2 ZMEDRUCK_PO                                                                               
    SY-MSGV3                                                                               
    SY-MSGV4                                                                               
    SY-MODNO 0                                                                               
    SY-DATUM 20080505                                                                               
    SY-UZEIT 190441                                                                               
    SY-XPROG SAPCNVE                                                                               
    SY-XFORM CONVERSION_EXIT

    Hi Prasad,
    Check the FM's
    SPELL_AMOUNT --> for display in millions
    HR_IN_CHG_INR_WRDS --> for display in lakhs and crores

  • Regarding purchase order Driver progrram

    Hi..,
    I am developing one smartform which is purchase order
    "/smb40/mmpo_l "
    and Driver programm is
    "/smb40/fm06p"
    i searched in TNAPR table but i didn't find driver program
    I am using ECC6.0
    can any one answer me how to download into "smb40" package
    replay to [email protected]
    waiting for geniues replay
    Thanks in advance

    Hi,
    You cannot enable the Copy From button on the purchase order window. This is because there is no originating document for a purchase order (which is the first document in the chain on the purchasing side).
    Perhaps if you explain your reasons for needing this functionality someone can come up with a suitable workaround.
    Kind Regards,
    Owen

  • Fail safe logic needed for purchase order upload program

    Hello all,
    i am working on creating PO's by reading data from a text file. I need to implement fail safe logic in it, which is to make sure this program uploads all the records in the text file successfully. For example, i have 1000 records in my text file and while running the upload program if the program times out while creating the 500th PO or if SAP is down at that time, then we have 499 PO's created and 501 yet to be created. But if we run the same program again, we will generate duplicate PO's for 499 again. I want to avoid this kind of problem.
    How do i implement this idea?
    Kindly guide me on this.
    Thanks.

    Ok ..
    Then I would suggest you use Application Log to keep the success and error messages of PO processing.
    You can check trsnaction SLG0 and create your own application log object.
    Then you need to use FMs BAL_LOG_* to crate and add messages to it.
    This way you will have a facility to check as which of your records are converted to PO for a run.
    In case SAP gets down in between , still you can find the details using Xn SLG1 and then accordingly remove the records from your file which are already converted to PO.
    Thanks,
    Ram

  • Error while submitting standard import purchase order program

    Hi,
    iam submitting Standard import purchase order concurrent program, iam getting
    error in view - output like
    Enter value for 12: EXEC FND_CONC_STAT.COLLECT;
    Enter value for 14:
    in view-log like
    To get the log messages for PDOI, please use the following id to query against FND_LOG_MESSAGES table:
    AUDSID = 10451963
    can any one help me?
    Regards
    Bhaskar

    Please paste the code here.. there may be some parameter issue while submission.

  • To find name for standard smartform of purchase order in Tcode me21n.......

    Please do not offer rewards
    Hi Abapers,
                 I had doubt, regarding how to find the name of standard smartform available for purchase order in tcode - ME21N.
              After executing ME21N, n print preview i get a form without logo. So i want to customize the form according to my clients requirement.For this i want to know the Smartform name, so tat i can copy to 'Z.....' and make the customization.
              Can anybody assist me overcome this problem of how to find out the name of smartform without knwing functionmodule name also....
                <<Text removed>>
    Advanced Thanks..............
    Edited by: Matt on Mar 25, 2009 10:26 AM

    DESIGN ONE SMARTFORM AS PERUR NEED.
    DRIVER PROGRAM FOR THISIS
    *& ZSAPFM06P
    &----     Print of a PO by SMART FORMS               *
    *& Purchase order printing program
    &----      FORM ENTRY
    SmartForm from customizing table TNAPR
    determine smartform function module for invoice
                    variant            = ' '
                    direct_call        = ' '
    control-no_open   = 'X'.
    control-no_close  = 'X'.
    call smartform invoice
                         archive_index        = toa_dara
                         archive_parameters   = arc_params
                    mail_appl_obj        =
                         mail_recipient       = ls_recipient
                         mail_sender          = ls_sender
                         output_options       = ls_composer_param
                         is_bil_invoice       = ls_bil_invoice
                         is_repeat            = repeat
              importing  job_output_info      = ls_job_info
                        document_output_info =
                        job_output_options   =
      error handling
       message id sy-msgid type sy-msgty number sy-msgno
               with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    analyse internal error table of Smart Forms
      add your handling
    REPORT ZSAPFM06P.
    TABLES: TNAPR,
            nast.
    DATA: lf_fm_name TYPE rs38l_fnam,
          lf_formname TYPE  tdsfname,
          control type ssfctrlop,
          errtab  type tsferror.
    FORM entry_neu using ent_retco ent_screen.
      lf_formname = tnapr-sform.
        CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
             EXPORTING  formname           = lf_formname
             IMPORTING  fm_name            = lf_fm_name
             EXCEPTIONS no_form            = 1
                        no_function_module = 2
                        OTHERS             = 3.
        IF sy-subrc <> 0.
          message id sy-msgid type sy-msgty number sy-msgno
                with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        ENDIF.
      control-no_dialog = 'X'.
      control-preview   = 'X'.
      control-langu     = sy-langu.
          CALL FUNCTION lf_fm_name
               EXPORTING
                           control_parameters   = control
                           user_settings        = 'X'
                           is_nast              = nast
               EXCEPTIONS formatting_error     = 1
                          internal_error       = 2
                          send_error           = 3
                          user_canceled        = 4
                          OTHERS               = 5.
      if sy-subrc <> 0.
        ent_retco = 0.
      else.
        ent_retco = 0.
      endif.
      call function 'SSF_READ_ERRORS'
           importing
                errortab = errtab.
      if not errtab is initial.
      endif.
    ENDFORM.
    DEFINE UR PROGRAM NAME AND SMARTFORM NAME IN NACE.

  • Open Purchase order pload

    Can any one provide OPen purchase order upload program using BAPI method....
    Thanks & regards.
    Ramesh T.
    Moderator Message : Not enough re-search before posting. Thread locked
    Edited by: Vinod Kumar on Apr 22, 2011 3:41 PM

    Hi Harshad,
    You can use the Service PO scenario.
    Service PO is used to Procure/ Avail the Services. you can create the service PO ( having account Assignment Category 'K' and item Category 'D'  for services) which has the validity period.
    at item overview level, you have to specify the Material /Service info in Short text.
    At Item Detail level, you will have the service tab. Depending on your indent (as and when it comes) you can enter the service item with its unit cost and qty.
    Later on, once you physically received the Material/Service, then using transaction ML81N you can accept the service. which in turn post your GR Document.
    Regards,
    S Anand

  • ESYU: Importing Standard Purchase Orders에서 문제 발생시 진단 방법

    Purpose
    Oracle Purchasing - Version: 11.5.10.2 to 12.0.6
    Information in this document applies to any platform.
    ConcurrentProgram:POXPOPDOI - Import Standard Purchase Orders
    이 문서는 reader게 Importing Standard Purchase Orders 실행 중 갑자기 발생하는 issue에 대해 어떻게
    대응하는지에 대한 자세한 정보를 제공한다.
    Instroduction
    Purchase Document Open Interface는 다량의 Standard Purchase Order는 Oracle Purchasing으로 빨리
    import 할 수 있게 한다. Import process는 import 되어야 하는 document information을 PO interface tables에
    넣어주는 작업을 필요로하며, data를 validate 하고 application에 PO를 생성하거나 error message를 return 하는
    Import Standard Purchase Orders concurrent program을 실행한다.
    이 문서의 목적은 Importing Standard Purchase Orders에 관련된 process를 이해하거나 갑자기 발생한 문제의
    원인을 찾는데 도움을 주기 위함이다. PO import 문제는 일반적으로 interface tables에 입력된 불일치하는 data가
    원인이며, 일단 문제가 확인되면 Metalink는 비슷한 문제를 찾아주거나 Oracle Support에 Service Request를 log
    할 수 있다.
    Test case Information
    1. 아래 insert 문장을 이용하여 PO interface tables에 data를 입력:
    INSERT INTO po.po_headers_interface
    (interface_header_id,
    action,
    org_id,
    document_type_code,
    currency_code,
    agent_id,
    vendor_name,
    vendor_site_code,
    ship_to_location,
    bill_to_location,
    reference_num)
    VALUES
    (apps.po_headers_interface_s.NEXTVAL,
    'ORIGINAL',
    207, -- Seattle
    'STANDARD',
    'USD', -- Your currency code
    24, -- Your buyer id stock
    'Advanced Network Devices',
    'FRESNO',
    'V1- New York City', -- Your ship to
    'V1- New York City', -- Your bill to
    'Currency test') -- Any reference num
    INSERT INTO po.po_lines_interface
    (interface_line_id,
    interface_header_id,
    line_num,
    shipment_num,
    line_type,
    item,
    uom_code,
    quantity,
    --unit_price,
    promised_date,
    ship_to_organization_code,
    ship_to_location)
    VALUES
    (po_lines_interface_s.nextval,
    po_headers_interface_s.currval,
    1,
    1,
    'Outside processing',
    'Flooring OSP',
    'Ea',
    1,
    --17.50,
    '10-APR-2009',
    'V1',
    'V1- New York City' )
    INSERT INTO po.po_distributions_interface
    (interface_header_id,
    interface_line_id,
    interface_distribution_id,
    distribution_num,
    quantity_ordered,
    charge_account_id)
    VALUES
    (po_headers_interface_s.currval,
    po.po_lines_interface_s.CURRVAL,
    po.po_distributions_interface_s.NEXTVAL,
    1,
    1,
    12975) -- Your Charge Account Id
    2. Interface tables에 data가 insert 되었다면 import progra을 실행전 정보를 확인하기 위해 아래 query 문을 이용한다.
    a - Select * from PO_HEADERS_INTERFACE where INTERFACE_HEADER_ID=&headerid
    b - Select * from PO_LINES_INTERFACE where INTERFACE_HEADER_ID=&headerid
    c - Select * from PO_DISTRIBUTIONS_INTERFACE where INTERFACE_HEADER_ID=&headerid
    3. Data를 review 했으면 Import Standard Purchase Orders program을 실행한다.
    Parameter >>
    Default Buyer: Null
    Create or Update Items: No
    Approval Status: INCOMPLETE
    Batch Id: Null
    4. 만일 program에 문제가 있어 error가 발생한다면 error의 원인을 제공하기 위해 Purchasing Interface Error Report를
    실행할 수 있다.
    Parameter >>
    Source Program: PO_DOCS_OPEN_INTERFACE
    Purge Data: No
    만일 PO가 import 되지 않았다면 Puchasing Interface Errors Report와 동일한 정보를 보기 위해 Interface Errors table을
    아래 SQL을 이용하여 조회할 수 있다.
    SELECT * FROM PO_INTERFACE_ERRORS WHERE INTERFACE_TRANSACTION_ID ='&recordsinterfacetransid';
    Diagnostics
    Import Standard Purchase ORder process의 troubleshoot 도움을 위해 아래 Diagnostics과 Reports를 이용한다.
    1. Diagnostics Tool : Oracle Purchasing Purchasing Documents Open Interface Data Collection Test
    (please refer to Note 224887.1 for assistance)
    이 Diagnostics는 import program에 의해 import 되는 data를 validate 할 것이며 missing 되거나 맞지않는 정보를 highlight 한다.
    이 Tool은 interface tables에 있는 맞지 않거나 불완전한 data의 자세한 정보를 제공할 수 있다.
    Error는 PO를 import 할 때 발생한 문제 분석을 시도하는데 매우 유익하므로 SR을 log시 이 Diagnostic output을 upload 하는
    것을 권장한다.
    2. Purchasing Interface Errors Report
    이 report는 Oracle Purchasing에서 사용가능하며 Import Standard Purchase Orders program을 실행시 발생하는
    error를 강조한다.
    Tracing
    11.5.10 이상의 version에서 Import Standard Purchase Orders program의 trace를 생성:
    1. Navigate to System Administrator responsibility
    2. Navigate to Profiles->System
    3. Query the Profile Option Concurrent: Allow Debugging and set it to Yes at User level
    4. Navigate to Purchasing responsibility
    5. From the Requests form, choose the Import Standard Purchase Orders program and set the required Parameters
    6. Click the Debug button
    7. Check the SQL Trace checkbox and specify Trace with Binds and Waits
    8. Submit the Concurrent program
    9. Retrieve the trace file created.
    Logging
    Import Standard Purchase Orders program의 FND Deug Log 생성:
    1. Log_seq를 아래 SQL을 이용하여 확인.
    select max(log_sequence) from fnd_log_messages;
    2. Set the following profiles at the user level:
    FND: Debug Log Enabled = YES
    FND: Debug Log Filename = NULL
    FND: Debug Log Level = STATEMENT
    FND: Debug Log Module = %
    3. Run Import Standard Purchase Orders program
    4. Using a SQL client run the following query :
    Select * from fnd_log_messages
    where log_sequence > &log_seq_noted_above
    order by log_sequence;
    이 query의 output은 Import Standard Purchase Orders program이 실행 중 발생한 error를 표시한다.
    Reference
    Note 781351.1

  • Purchase Order Import inserts duplicate records in po_line_locations

    Hi,
    I'm running standard Purchase Order Import program to import few PO's. We have only one shipment for each item, so its only one record for each line in po_line_locations. But after running the import, it inserts a duplicate record with same qty into po_line_locations. Basically it is inserting same item twice in po_line_locations_all table and quantity is getting doubles at the line level. Seached Metalink but no hits for this, till now.
    This is in R12 (12.0.6).
    Did anyone encounter this problem earlier? Any hints or comments would help.
    Thanks in advance.
    Edited by: user2343071 on Sep 2, 2009 3:54 PM

    Hi,
    Once you please debug the particular program with the help of ABAPer. That may resolve your issue. Thanking you

  • Purchase Order with FX Cover

    Hi there,
    If I raise a purchase order and have also arranged FX cover for this amount, in the PO I can select fixed exchange rate, so that this is recorded correctly. 
    However, if the purchase requires multiple part payments at different rates, how can I correctly record these on the PO if there is only one field and at the header level. 
    entering a weighted average on the PO results in fx gains/losses that net out, but are not required.
    Anyone come accross this scenario?  It is not common, but also should not be unique.

    [Create Purchase order with program|can we create purchase order through report programming?]
    Plz be clear about your requirement instead of posting questions like these.
    Don't violate forum rules with Duplicate posts

Maybe you are looking for