Unable to create Local PO's in SRM

Hi,
Earlier, we working with Classic and Local scenerio's. Now we activated Extended classic for certain product categories.
Issue: we unable to create Local PO's - we getting error message that
1.Account system (SRM) differ than target system (R/3)
2.Sytem asking us to enter Plant .However, if we enter the plant , getting another error message that material not maintained in the plant (R/3).
It seems ,eventhough it is Local category system promting as a backend proct category.
Could you help us?
Harish

Hi Harish
You can create a local PO for local product categorybut that same material group must exist in r/3 system  which you created in SRM.
there are some instances , for eg.
001- material group in r/3 same you can create 001 product category in srm .
but wherever you mentioned product category originated logical system as SR logical system.
for eg define product category settings source system as Local SRM logical system and target system as r/3 backend system.
hope you understand.
Try for product category dont try for product . (only special request.)
regards
muthu

Similar Messages

  • Unable to Create local Adjustment in RAW

    I was editing my images on RAW when all of a sudden I guess I pressed an incorrect key (yeah you know those split seconds where something happened and you dont know what you did) and now everytime I want to use the Graduated Filter tool or the Adjustment Brush tool and I press on top of the image it gives me the following message:
    ERROR:
    Unable to Create Local Adjustment. All the local adjustment controls are set to have
    no effect on this image
    It doesnt work on ANY raw images now, I tried pressing "Reset Camera Raw Defaults" and it still doesnt work.
    Is there a setting that I moved without noticing??
    At the time this happened I had 6 pictures on camera Raw I had synchronized them and I was doing small adjustments to one of the images, I had finished using the Graduated Filter tool on an image when then all of a sudden it stopped working
    Thank you for your help!! I need to finish this project today and now I am going to have to sit and wait to resolve. Thanks again

    golftragic wrote:
    I'm having the same 'Unable to create local adjustment …' problem too. But I don't understand the answer, specifically what 'values' should be modified, where do I find them to modify, and what kind of modification. Apologies for my ignorance, but I can't find anything despite searching the forums as well as I can.
    Values on the sliders in the box on the right of the picture.
    And next time try F1 before you waste time using the clunky forum search.

  • How do I fix the problem of unable to create local adjustments in raw

    It used to work when I first installed Cs5 and now gradients and gradient brus just comes up with the error that All local adjustment controls are set to have no effect on the image. How do I fix this problem?

    Try changing the values of the sliders in the panel to the right first.  I think it's telling you they're all just set (e.g., center scale) so that you won't see any results from the tool.
    -Noel

  • Unable to create local adjustment

    Using CS5 and all has been working fine u
    p to now. I tried to use
    one of the local adjustment tools (Graduated Filter) and got th
    e following message "All the local adjustment tools
    are set to have no effecton the image". What has happened????    They worked fin
    e 5 minutes ago. Any suggestions as to how to fix the problem are appreciated.
    Thanks
    John A.
    CS5, Windows Vista

    Thanks Zeno. I will
    try that. Appreciate you taking time to respond!!!
    John A.

  • SRM 7.0  Unable to create PO - Classic Scenario.

    Hello,
    We are able to successfully create the below scenario.
    PR in ECC --> Get PR in SRM --> Start Collective processing -> Transfer to Central System (SC is created for the PR @ this time) --> Create RFx --> Rfx Response --> Create PO. (PO is created in ERP, Classic Scenario)
    We are able to get the PR & we are able to create SC successfully and the PR/ SC is available in Sourcing cocpit.
    Able to create RFx --> Rfx Response.
    Now once the RFx Response is Accepted --> We go for creating PO.
    Classic Scenario.
    The error is due to pricing - debugged and checked as mentioned in my earlier message.
    IPC pricing is switched off and the BADI for simple pricing is activated.
    Error :   " Message A BBP_PD 396 cannot be processed in plugin mode HTTP "
    But this is due to pricing is what i guess.
    Error is raised in FM "BBP_PDPRC_UPDATE".
    Kindly Suggest.
    Unable to Create PO
    Regards.
    Edited by: Purshothaman P on Jul 6, 2010 1:50 PM

    Hi,
    Please check and run the following reports (se38): BBP_CND_CUSTOMIZING_CHECK & RSVMCRT_HEALTH_CHECK and post back the results.
    Note for BBP_CND_CUSTOMIZING_CHECK also run 'Simulation of Pricing with Manual Price' (scroll down after executing the report initially).
    Also the badi information you activated tells us a lot. Although i take it that you executed and read everything that's included in the transaction information. The following sentence gives a prety doubtfull feeling for the CPPR scenario to work for your configuration:
    SAP recommends using this BAdI only in exceptional cases and only after checking thoroughly if it is compatible with the Business Scenarios used.
    Note: From what i've just read IPC has to be disabled, certain badi's etc. need to be disabled. And VMC (sap basis) has to be configured. Please view: [http://help.sap.com/SCENARIOS_BUS2008/helpdata/EN/9C/F90B7CB34A4889935D1733C6756D5B/content.htm]
    Could you also please check and provide whether 'normal' SRM classic scenarios like: SC -> PO do run within your system. Also the error and information you have provided is very little.
    Kind regards,
    Tim

  • Unable to create confirmation/invoice in SRM,Classic Scenario

    Hi Guru's,
    I am unable to create Confirmation/Invoice in the Portal, attached the screen shot of the error
    its is the problem with the ADRC table, there is no entry in the table for the BP.
    I tried to access the table via SM30 to add the entry in ADRC manually, I get a message table maintenance not defined
    Regards,
    Kiran

    Hi Kiran,
    Could you please also advise whether all the users are not able to create the confirmation in portal. Or if there is any specific user who is not able to do that?
    And I also request you to advise whether you going to do the invoice in SRM portal in classic scenario?
    Best Regards,
    Bharathi

  • Creating Local Product in SRM System.

    Hi All,
    I want to create Local Material in SRM system.
    while creating i am getting error.
    1) Set type 380BDF7B502D63F7E10000009B38FA0B does not exist.
    in table TADIR there is no set type : COMM_PR_SHTEXT.
    while mantaing this it is asking for Package.
    can any help to resolve this issue by saying what is the package for this object.
    thanks and regards.
    Kalyan

    Hi,
    See these related threads for more pointers:
    Attribute does nit exist after the upgrade
    Re: Standalone scenario
    Re: create a product
    BR,
    Disha.
    Do reward points for  useful answers.

  • Extended Classic : Unable to create purchase order

    Hi All,
    We are using SRM5.0 system, i did required configuration for extended classic. I defined number ranges for local and backend purchase orders. But after creating SC, system is unable to create purchase order. Shopping cart is not ended up in error. In BBP_PD, I found that number generated for purchase order is always 1.
    Please advise.
    Regards,
    Raj

    are the RFC connections between SRM system and R/3 systems working? please check this.
    transaction --> SM59 --> is used for maintaining RFC destination.

  • Unable to Create PO

    Is there a way to tell the System that WE ARE NOT TRYING TO CREATE A LOCAL PO & We would want to create the PO in ECC directly?
    Inorder to execute the below code & skip the First Block of the Below code & Perform the Second Block.
    Second Block is PERFORM CLASSIC_LIGHT_PRICING.
    In debugging mode i_object_type is having value "BUS2201" & C_PO is having value "BUS2201", So the control enters the first part of the below code & RAISES THE ERROR.
    Code from Function Module "BBP_PDPRC_UPDATE" :
    IF i_object_type = c_po.
    PERFORM error_message USING c_msgty_a gc_msgid_bbp_pd
    gc_prc_msg_simplpricepo gc_no.
    ELSE.
    PERFORM classic_light_pricing
    TABLES it_pridoc
    USING i_com
    i_p_guid i_inp_guid
    CHANGING e_com
    ev_price_unit.
    ENDIF.
    --> Are there some relavent Notes to resolve this issue?

    Hello,
    Small Update....
    Our scenarios is:
    SC -> Sourcing -> RFx -> RFx Response -> PO in ERP (
    Directly create PO in ERP )
    We are able to successfully create the below scenario.
    PR in ECC --> Get PR in SRM --> Start Collective processing -> Transfer to Central System (SC is created for the PR @ this time) --> Create RFx --> Rfx Response --> Create PO. (PO is created in ERP, Classic Scenario)
    We are able to get the PR & we are able to create SC successfully and the PR/ SC is available in Sourcing cocpit.
    Able to create RFx --> Rfx Response.
    Now once the RFx Response is Accepted --> We go for creating PO.
    The same error. We are unable to create PO.
    The error is due to pricing - debugged and checked as mentioned in my earlier message.
    Kindly Suggest.
    Unable to Create PO
    Regards.

  • Unable to create IDOCs after client copy

    I'm unable to create IDOCs after a client copy.  I receive a SAPSQL_ARRAY_INSERT_DUPREC or insert of duplicate rows ABAP dump.
    Does anyone know what how to fix this.  Thank you in advance.
    Runtime Error          SAPSQL_ARRAY_INSERT_DUPREC
    Except.                CX_SY_OPEN_SQL_DB
    Date and Time          22.10.2007 16:50:51
    ShrtText
    The ABAP/4 Open SQL array insert results in duplicate database records.
    What happened?
    Error in ABAP application program.
    The current ABAP program "SAPLEDI1" had to be terminated because one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    What can you do?
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    is especially useful if you want to keep a particular message.
    Error analysis
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
    neither
    caught nor passed along using a RAISING clause, in the procedure
    "F09_IDOC_INSERT_WITH_NUMBER" "(FORM)"
    Since the caller of the procedure could not have expected this exception
    to occur, the running program was terminated.
    The reason for the exception is:
    If you use an ABAP/4 Open SQL array insert to insert a record in
    the database and that record already exists with the same key,
    this results in a termination.
    (With an ABAP/4 Open SQL single record insert in the same error
    situation, processing does not terminate, but SY-SUBRC is set to 4.)
    How to correct the error
    Use an ABAP/4 Open SQL array insert only if you are sure that none of
    the records passed already exists in the database.
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
    "SAPSQL_ARRAY_INSERT_DUPREC" CX_SY_OPEN_SQL_DBC
    "SAPLEDI1" or "LEDI1F09"
    "F09_IDOC_INSERT_WITH_NUMBER"
    If you cannot solve the problem yourself and you wish to send
    an error message to SAP, include the following documents:
    1. A printout of the problem description (short dump)
    To obtain this, select in the current display "System->List->
    Save->Local File (unconverted)".
    2. A suitable printout of the system log
    To obtain this, call the system log through transaction SM21.
    Limit the time interval to 10 minutes before and 5 minutes
    after the short dump. In the display, then select the function
    "System->List->Save->Local File (unconverted)".
    3. If the programs are your own programs or modified SAP programs,
    supply the source code.
    To do this, select the Editor function "Further Utilities->
    Upload/Download->Download".
    4. Details regarding the conditions under which the error occurred
    or which actions and input led to the error.
    The exception must either be prevented, caught within the procedure
    "F09_IDOC_INSERT_WITH_NUMBER"
    "(FORM)", or declared in the procedure's RAISING clause.
    To prevent the exception, note the following:
    System environment
    SAP Release.............. "640"
    Application server....... "auaplxr3q"
    Network address.......... "128.197.135.5"
    Operating system......... "AIX"
    Release.................. "5.3"
    Hardware type............ "000B439ED600"
    Character length......... 8 Bits
    Pointer length........... 64 Bits
    Work process number...... 1
    Short dump setting....... "full"
    Database server.......... "auaplxr3q"
    Database type............ "ORACLE"
    Database name............ "Q63"
    Database owner........... "SAPR3"
    Character set............ "en_US.ISO8859-1"
    SAP kernel............... "640"
    Created on............... "Mar 22 2007 20:48:46"
    Created in............... "AIX 1 5 00538A4A4C00"
    Database version......... "OCI_920 "
    Patch level.............. "175"
    Patch text............... " "
    Supported environment....
    Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
    10.2.0.."
    SAP database version..... "640"
    Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
    Memory usage.............
    Roll..................... 16128
    EM....................... 4189928
    Heap..................... 0
    Page..................... 0
    MM Used.................. 1469352
    MM Free.................. 2718056
    SAP Release.............. "640"
    User and Transaction
    Information on where terminated
    The termination occurred in the ABAP program "SAPLEDI1" in
    "F09_IDOC_INSERT_WITH_NUMBER".
    The main program was "SAPMSSY1 ".
    The termination occurred in line 108 of the source code of the (Include)
    program "LEDI1F09"
    of the source code of program "LEDI1F09" (when calling the editor 1080).
    Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
    the
    procedure "F09_IDOC_INSERT_WITH_NUMBER" "(FORM)" but was not handled locally,
    not declared in the
    RAISING clause of the procedure.
    The procedure is in the program "SAPLEDI1 ". Its source code starts in line 5
    of the (Include) program "LEDI1F09 ".
    Source Code Extract
    Line
    SourceCde
    78
    perform call_badi tables list_container_insert
    79
    using  control
    80
    ident.
    81
    Aufruf des Badi's für das einstreuen neuer Segmente
    82
    perform call_insert_badi tables list_container_insert
    83
    using control
    84
    ident
    85
    changing maxsegnum.
    86
    87
       free list_container_insert
    88
    FREE_RETURN = 1.
    89
    ELSE. " no other IDoc is open in create-mode
    90
    LOOP AT LIST_CONTAINER_CREATE WHERE MANDT EQ SY-MANDT
    91
    AND   DOCNUM EQ IDENT.
    92
    LIST_CONTAINER_CREATE-DOCNUM = DOCNUM.
    93
    MODIFY LIST_CONTAINER_CREATE.
    94
    ADD 1 TO MAXSEGNUM.
    95
    ENDLOOP.
    96
    if control-mestyp eq c_mestyp.
    97
    CALL FUNCTION 'FUNCTION_EXISTS'
    98
    EXPORTING
    99
    funcname           = c_func
    100
    EXCEPTIONS
    101
    FUNCTION_NOT_EXIST = 1.
    102
    IF syst-subrc IS INITIAL.  "Anwendungssystem
    103
    perform call_transform
    104
    tables list_container_create
    105
    using  control.
    106
    ENDIF.
    107
    endif.
    >>>>>
    INSERT EDID4 FROM TABLE LIST_CONTAINER_CREATE.
    109
    Aufruf des Badi's für das Anwendungsmapping einzelner Felder
    110
    perform call_badi tables list_container_create
    111
    using  control
    112
    ident.
    113
    perform call_insert_badi tables list_container_create
    114
    using  control
    115
    ident
    116
    changing maxsegnum.
    117
    118
      free list_container_create
    119
    FREE_RETURN = 0.
    120
    ENDIF.
    121
    122
    insert status records
    123
    124
    SYN_ERROR_IN = ' '.
    125
    CNTR_STATUS = 0.
    126
    REFRESH LIST_STATUS.
    127
    CLEAR LIST_STATUS.
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    2
    SY-TABIX
    1
    SY-DBCNT
    1
    SY-FDPOS
    0
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    SY-UCOMM
    SY-TITLE
    CPIC and RFC Control
    SY-MSGTY
    SY-MSGID
    SY-MSGNO
    000
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    13 FORM         SAPLEDI1                            LEDI1F09                              108
    F09_IDOC_INSERT_WITH_NUMBER
    12 FUNCTION     SAPLEDI1                            LEDI1U19                               33
    EDI_DOCUMENT_CLOSE_CREATE_TAB
    11 FUNCTION     SAPLEDIR                            LEDIRU01                              273
    IDOC_INBOUND_WRITE_TO_DB
    10 FORM         SAPLEDIN                            LEDINF01                              457
    ONE_IDOC_STORE
    9 FUNCTION     SAPLEDIN                            LEDINU05                              234
    IDOC_INBOUND_ASYNCHRONOUS
    8 FORM         SAPLEDIN                            LEDINV05                               19
    IDOC_INBOUND_ASYNCHRONOUS
    7 FORM         SAPMSSY1                            SAPMSSY1                              254
    XAB_RUN_DRIVER
    6 FUNCTION     SAPLSXAB                            LSXABU01                                9
    RFC_RUN_XAB_DRIVER
    5 FUNCTION     SAPLERFC                            LERFCU01                               59
    ARFC_EXECUTE
    4 FUNCTION     SAPLERFC                            LERFCU02                              229
    ARFC_DEST_SHIP
    3 FORM         SAPLERFC                            LERFCV02                               28
    ARFC_DEST_SHIP
    2 FORM         SAPMSSY1                            SAPMSSY1                               69
    REMOTE_FUNCTION_CALL
    1 MODULE (PBO) SAPMSSY1                            SAPMSSY1                               30
    %_RFC_START
    Chosen variables
    Name
    Val.
    No.      13 Ty.          FORM
    Name  F09_IDOC_INSERT_WITH_NUMBER
    CONTROL-MESTYP
    USERCLONE
    554544444222222222222222222222
    53523CFE5000000000000000000000
    C_MESTYP
    FIDCCH
    444444222222222222222222222222
    694338000000000000000000000000
    SY-XFORM
    IDOC_INBOUND_ASYNCHRONOUS
    444454444544545544454445522222
    94F3F9E2F5E4F139E382FEF5300000
    LIST_STATUS-STAPA2
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    C_FUNC
    IDOC_TRANSFORM
    444455544544542222222222222222
    94F3F421E36F2D0000000000000000
    SYST-REPID
    SAPLEDI1
    5454444322222222222222222222222222222222
    310C549100000000000000000000000000000000
    SY-UNAME
    Q63CLNT140
    533444533322
    1633CE414000
    %_DUMMY$$
    2222
    0000
    SY-MSGV1
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    SYST-SUBRC
    0
    0000
    0000
    ALE_IDOC_TO_APL_OK
    62
    33
    62
    LIST_CONTAINER_CREATE[]
    Table IT_20[9x1068]
    FUNCTION-POOL=EDI1DATA=LIST_CONTAINER_CREATE[]
    Table reference: 14
    TABH+  0(20) = 070000008036F5B8000000000000000000000000
    TABH+ 20(20) = 0000000E00000014000000090000042CFFFFFFFF
    TABH+ 40(16) = 0400002300000CA0000824C401000000
    store        = 0x070000008036F5B8
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 14    (0x0000000E)
    label        = 20    (0x00000014)
    fill         = 9     (0x00000009)
    leng         = 1068  (0x0000042C)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000048
    occu         = 8     (0x00000008)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x070000008036F610
    pghook       = 0x07000000802D86D0
    idxPtr       = 0x0000000000000000
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x00000010)
    lineAlloc    = 16    (0x00000010)
    store_id     = 23    (0x00000017)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    hsdir        = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    LIST_CONTAINER_CREATE
    1400000000000511747000000009E1BPADRML                     00000002#èXD63        070TST_QA140_1
    3333333333333333333333333333434544544222222222222222222222333333330E54332222222233355555433353
    14000000000005117470000000095120142DC0000000000000000000000000000238846300000000070434F11140F1
    CONTROL
    1400000000000511747640 64        2SAPQ63    LSQ63CLNT140
    3333333333333333333333233222222223545533222245533444533322222222222222222222222222222222222222
    14000000000005117476400640000000023101630000C31633CE414000000000000000000000000000000000000000
    G_MAXSYNERR
    1
    0000
    0001
    <%_TABLE_EDID4>
    ALE_DISPATCH_ERROR
    27
    33
    27
    ALE_IDOC_READY_FOR_APL
    64
    33
    64
    %_SPACE
    2
    0
    IDENT
    0000000000000001
    3333333333333333
    0000000000000001
    ALE_IDOC_TO_APL_ERROR
    63
    33
    63
    No.      12 Ty.          FUNCTION
    Name  EDI_DOCUMENT_CLOSE_CREATE_TAB
    IDENTIFIER
    0000000000000001
    3333333333333333
    0000000000000001
    NO_DEQUEUE
    X
    5
    8
    SYN_ACTIVE
    Y
    5
    9
    IDOC_CONTROL
    1400000000000511747640 64        2SAPQ63    LSQ63CLNT140
    3333333333333333333333233222222223545533222245533444533322222222222222222222222222222222222222
    14000000000005117476400640000000023101630000C31633CE414000000000000000000000000000000000000000
    SYNTAX_RETURN
    0
    0000
    0000
    INT_EDIDD[]
    Table IT_10[9x1062]
    FUNCTION-POOL=EDINDATA=G_T_DATA_RECORDS[]
    Table reference: 9
    TABH+  0(20) = 0700000080284B80070000008028530800000000
    TABH+ 20(20) = 000000090000000A0000000900000426FFFFFFFF
    TABH+ 40(16) = 0400000900000AA8000824C401000000
    store        = 0x0700000080284B80
    ext1         = 0x0700000080285308
    shmId        = 0     (0x00000000)
    id           = 9     (0x00000009)
    label        = 10    (0x0000000A)
    fill         = 9     (0x00000009)
    leng         = 1062  (0x00000426)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000039
    occu         = 8     (0x00000008)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x0700000080320D90
    pghook       = 0x07000000802E1508
    idxPtr       = 0x0000000000000000
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x00000010)
    lineAlloc    = 16    (0x00000010)
    store_id     = 17    (0x00000011)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    hsdir        = 0x0000000000000000
    ext2         = 0x07000000802852A8
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x0700000080284B30
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    NO_IGNORE
    2
    0
    EDI_IDOC_SYNTAX_ERROR_IN
    60
    33
    60
    DOCNUM
    0000000000511747
    3333333333333333
    0000000000511747
    EXCLUSIVE
    E
    4
    5
    SYNCHRONOUS
    S
    5
    3
    APL_TESTIDOC_CHECK_OK
    55
    33
    55
    FREE_RETURN
    0
    0000
    0000
    INT_EDIDD
    1400000000000000001000009E1BPADRML                  00000000##XD63        070TST_QA140_17  X00
    3333333333333333333333333434544544222222222222222222333333330054332222222233355555433353322533
    14000000000000000010000095120142DC0000000000000000000000000000846300000000070434F11140F1700800
    SUB_INT_ACK_POSITIVE
    14
    33
    14
    G_INSERT_OK
    2
    0
    LIST_CONTAINER_INSERT_TMP[]
    Table[initial]
    LIST_CONTAINER_INSERT_TMP
    0000000000000000000000000                              00000000##
    2223333333333333333333333333222222222222222222222222222222333333330022222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    %_ARCHIVE
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    No.      11 Ty.          FUNCTION
    Name  IDOC_INBOUND_WRITE_TO_DB
    PI_DO_HANDLE_ERROR
    X
    5
    8
    PI_NO_DEQUEUE
    X
    5
    8
    PI_RETURN_DATA_FLAG
    X
    5
    8
    PI_RFC_MULTI_CP
    0000
    3333
    0000
    PI_STATUS_MESSAGE
    000000000000000000000000000000000000000000000000000000000000
    2223333333333333333333333333333333333333333333333333333333333332222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    PE_IDOC_NUMBER
    0000000000000001
    3333333333333333
    0000000000000001
    PE_INBOUND_PROCESS_DATA
    140BAPI                                                  6
    3334454222222222222222222222222222222222222222222222222223222222222222222222222222222222222222
    1402109000000000000000000000000000000000000000000000000006000000000000000000000000000000000000
    PE_STATE_OF_PROCESSING
    0
    0000
    0000
    T_DATA_RECORDS[]
    Table IT_10[9x1062]
    T_LINKED_OBJECTS[]
    Table IT_11[0x100]
    FUNCTION-POOL=EDINFORM=ONE_IDOC_STOREDATA=LT_LINKED_OBJECTS[]
    Table reference: 10
    TABH+  0(20) = 000000000000000007000000802853F000000000
    TABH+ 20(20) = 0000000A0000000B0000000000000064FFFFFFFF
    TABH+ 40(16) = 0400000900002BB00010249401000000
    store        = 0x0000000000000000
    ext1         = 0x07000000802853F0
    shmId        = 0     (0x00000000)
    id           = 10    (0x0000000A)
    label        = 11    (0x0000000B)
    fill         = 0     (0x00000000)
    leng         = 100   (0x00000064)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000190
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    store_id     = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    hsdir        = 0x0000000000000000
    ext2         = 0x0700000080285390
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x0700000080285340
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    PC_CONTROL_RECORD
    1400000000000000000    30        2          LSQ63CLNT140
    3333333333333333333222233222222223222222222245533444533322222222222222222222222222222222222222
    14000000000000000000000300000000020000000000C31633CE414000000000000000000000000000000000000000
    %_VIASELSCR
    0
    4
    %_SPACE
    2
    0
    L_STATUS
    64
    33
    64
    L_ALE_SUCCESS_MESSAGE
    B1                  S005                                                  No filters
    4322222222222222222253332222222222222222222222222222222222222222222222222246266676772222222222
    21000000000000000000300500000000000000000000000000000000000000000000000000EF069C45230000000000
    ST_PREVIOUS_PARTNER_DATA-SYNCHK
    X
    5
    8
    C_TRUE
    X
    5
    8
    SYST-REPID
    SAPLEDIR
    5454444522222222222222222222222222222222
    310C549200000000000000000000000000000000
    C_ELEMENT_UNPROCESSED_IDOCS
    Unprocessed_IDocs
    56776667766544667222222222222222
    5E02F353354F94F33000000000000000
    ST_PREVIOUS_STATE_OF_PROCE
    0
    0000
    0000
    ST_INBOUND_PROCESS_DATA-EDIVR2
    6
    3
    6
    SY-MSGV4
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    L_SYN_ACTIVE
    Y
    5
    9
    SY-XFORM
    IDOC_INBOUND_ASYNCHRONOUS
    444454444544545544454445522222
    94F3F9E2F5E4F139E382FEF5300000
    L_SYNTAX_RETURN
    0
    0000
    0000
    %_DUMMY$$
    2222
    0000
    SY-REPID
    SAPLEDIR
    5454444522222222222222222222222222222222
    310C549200000000000000000000000000000000
    No.      10 Ty.          FORM
    Name  ONE_IDOC_STORE
    IDOC_NUMBER_IN
    0000000000000000
    3333333333333333
    0000000000000000
    STATE_OF_PROCESSING_IN
    0
    0000
    0000
    INBOUND_PROCESS_DATA_IN
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    GT_NEW_IDOC_IDENTIFICATIONS[]
    Table[initial]
    G_LAST_IDOC_NUMBER
    0000000000000000
    3333333333333333
    0000000000000000
    SYST-REPID
    SAPLEDIN
    5454444422222222222222222222222222222222
    310C549E00000000000000000000000000000000
    CURRENT_CONTROL_RECORD_IN-DOCNUM
    0000000000000000
    3333333333333333
    0000000000000000
    CONV_ERROR
    2
    0
    C_TRUE
    X
    5
    8
    SY
    0000000000000000000000000000000000000000000000000000000000000000000000000000000200000000000000
    0002000000010009000000000000000000000000000100000001000000010000000000000000004C00000000000000
    STATUS_MESSAGE_IN
    000000000000000000000000000000000000000000000000000000000000
    2223333333333333333333333333333333333333333333333333333333333332222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    C_IDOC_SELECT_AND_WRITE_TO_DB
    5
    3
    5
    SY-REPID
    SAPLEDIN
    5454444422222222222222222222222222222222
    310C549E00000000000000000000000000000000
    STATUS_MESSAGE_IN-STAMID
    22222222222222222222
    00000000000000000000
    GT_NEW_IDOC_IDENTIFICATIONS
    0000000000000000
    3333333333333333222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SPACE
    2
    0
    STATUS_MESSAGE_IN-STAMNO
    000
    333
    000
    RET_FLAG
    X
    5
    8
    G_RFC_CODEPAGE
    0000
    3333
    0000
    RSJOBINFO-JOBSUBRC
    0
    0000
    0000
    SY-XFORM
    IDOC_INBOUND_ASYNCHRONOUS
    444454444544545544454445522222
    94F3F9E2F5E4F139E382FEF5300000
    SY-LANGU
    E
    4
    5
    G_T_DATA_RECORDS[]
    Table IT_10[9x1062]
    LT_LINKED_OBJECTS[]
    Table IT_11[0x100]
    CURRENT_CONTROL_RECORD_IN
    1400000000000000000    30        2          LSQ63CLNT140
    3333333333333333333222233222222223222222222245533444533322222222222222222222222222222222222222
    14000000000000000000000300000000020000000000C31633CE414000000000000000000000000000000000000000
    %_DUMMY$$
    2222
    0000
    SWO_%OBJID
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    No.       9 Ty.          FUNCTION
    Name  IDOC_INBOUND_ASYNCHRONOUS
    IDOC_CONTROL_REC_40[]
    Table IT_3[1x524]
    FUNCTION-POOL=EDINFORM=IDOC_INBOUND_ASYNCHRONOUSDATA=IDOC_CONTROL_REC_40[]
    Table reference: 3
    TABH+  0(20) = 07000000802D876007000000802D449000000000
    TABH+ 20(20) = 0000000300000003000000010000020C000000E0
    TABH+ 40(16) = 0400000900001FE0000A249001000000
    store        = 0x07000000802D8760
    ext1         = 0x07000000802D4490
    shmId        = 0     (0x00000000)
    id           = 3     (0x00000003)
    label        = 3     (0x00000003)
    fill         = 1     (0x00000001)
    leng         = 524   (0x0000020C)
    loop         = 224   (0x000000E0)
    xtyp         = TYPE#000136
    occu         = 10    (0x0000000A)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 0
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x07000000802DB9D8
    pghook       = 0x0000000000000000
    idxPtr       = 0x0000000000000000
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 10    (0x0000000A)
    lineAlloc    = 10    (0x0000000A)
    store_id     = 9     (0x00000009)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    hsdir        = 0x0000000000000000
    ext2         = 0x07000000802D88A0
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x07000000802D8710
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    IDOC_DATA_REC_40[]
    Table IT_4[9x1063]
    FUNCTION-POOL=EDINFORM=IDOC_INBOUND_ASYNCHRONOUSDATA=IDOC_DATA_REC_40[]
    Table reference: 4
    TABH+  0(20) = 07000000802D880807000000802D896000000000
    TABH+ 20(20) = 00000004000000040000000900000427FFFFFFFF
    TABH+ 40(16) = 04000009000020500008249001000000
    store        = 0x07000000802D8808
    ext1         = 0x07000000802D8960
    shmId        = 0     (0x00000000)
    id           = 4     (0x00000004)
    label        = 4     (0x00000004)
    fill         = 9     (0x00000009)
    leng         = 1063  (0x00000427)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000138
    occu         = 8     (0x00000008)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 0
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x07000000802E1550
    pghook       = 0x07000000802D8860
    idxPtr       = 0x0000000000000000
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x00000010)
    lineAlloc    = 16    (0x00000010)
    store_id     = 12    (0x0000000C)
    shmIsReadOnly = 0     (0x

    Hi Rohan,
    Welcome to SDN!
    This error means that you're trying to duplicate a record on the DB... check the IDOC  number ranges... it might help
    Regards
    Juan
    Please reward with points if helpful

  • Getting error while creating form and report on webservice: ORA-20001: Unable to create form on table. ORA-02263: need to specify the datatype for this column.

    i am using the following description to create a web service reference:
    web reference :REST
    Name :Yahoo Map
    URL :http://local.yahooapis.com/MapsService/V1/mapImage
    HTTP Method: GET
    Basic Authentication: No
    Add Parameter:
    Name       Type
    appid        String
    location    String
    Output Format: XML
    XPath to Output Parameters : /Result
    Output Parameter:
    Name       Path       Type
    Url          /text()      String
    Then i tried to create form and report on webservice:
    Web Service Reference Type: Yahoo Map
    Operation: doREST
    All the fields i keep as default
    I tick the checkbox (url)in report Parameter
    After clicking next whereever required i click create button
    I get the following error
    ORA-20001: Unable to create form on table. ORA-02263: need to specify the datatype for this column.
    Please someone help to solve this as i need to fix it urgently.

    i exported the application from apex.oracle.com and imported it to our environment
    import went fine, but when I ran the IR page I got
    ORA-20001: get_dbms_sql_cursor error ORA-00904: : invalid identifier
    evidently the problem is a lack of public execute on DBMS_LOB, which is used in the generated IR source.
    while waiting for the DBA to grant privs on DBMS_LOB, changing the dbms_lob.getlength call to length() fixes the IR.
    however, i am not getting the download link on the associated form page... changed templates, that's not the issue -- we'll see if that's a dbms_lob issue as well

  • APEX:Getting error while creating form and report on webservice: ORA-20001: Unable to create form on table. ORA-02263: need to specify the datatype for this column.

    I am using Apex 4.2.2.00.11
    am using the following description to create a web service reference:
    web reference :REST
    Name :Yahoo Map
    URL :http://local.yahooapis.com/MapsService/V1/mapImage
    HTTP Method: GET
    Basic Authentication: No
    Add Parameter:
    Name       Type
    appid        String
    location    String
    Output Format: XML
    XPath to Output Parameters : /Result
    Output Parameter:
    Name       Path       Type
    Url          /text()      String
    Then i tried to create form and report on webservice:
    Web Service Reference Type: Yahoo Map
    Operation: doREST
    All the fields i keep as default
    I tick the checkbox (url)in report Parameter
    After clicking next whereever required i click create button
    I get the following error
    ORA-20001: Unable to create form on table. ORA-02263: need to specify the datatype for this column.
    Please someone help to solve this as i need to fix it urgently.

    336554,
    Looks like there is a 127-column limit on the number of report columns supported when using that wizard. Do you have more than that?
    57434

  • Unable to create a PO(in backend system) in ECS

    Hello all,
    I used the FM BBP_PD_SC_CREATE, BBP_PD_SC_UPDATE, BBP_PD_SC_SAVE to create a shopping cart in ECS scenario.
    The problem is I am unable to create a PO in the backend system for the shopping cart. I am also getting the message 'Vendor 3000014598 not intended for purch. org. Ref: MM Purchasing Org'.
    Please help me in this context.
    Thanks,
    Vishnu

    Hi,
    The problem with organization structure , Please check your organizaiton structure.
    Change company code /Pur.org Separatlly it will work.
    while replicating vendor please select the flag 'with out reference to back end pur.org' and choose local purchasing organization.
    refer this link
    Vendor xxxxxxx not intended for purch. org. xxxx Purchasing Organization
    Thanks
    prasad .s

  • Unable to create a file in Application Server using OPEN DATASET stattement.

    I am unable to create a file in Application Server using the following statement.
    OPEN DATASET filename FOR OUTPUT
    IN TEXT MODE ENCODING DEFAULT
    MESSAGE msg.
    The message I'm getting is "Permission Denied". I have checked authorisation using SU53 which says "The last authorization check was successful". Please help.

    You can use following code to capture the error.
    TRY.
          OPEN DATASET filename FOR OUTPUT IN BINARY MODE MESSAGE V_MSG.
          CATCH CX_ROOT
          INTO EXCEPTION.
          CALL METHOD O_EXCEPTION ->IF_MESSAGE~GET_TEXT
            RECEIVING
            RESULT = V_MSG.
          MESSAGE v_msg
          TYPE 'E'.
    ENDTRY.
    You can capture error in v_msg.
    Following are the exceptions for the same:
    Exceptions
    Catchable Exceptions
    CX_SY_FILE_OPEN
    Cause: The file is already open.
    Runtime Error: DATASET_REOPEN
      CX_SY_CODEPAGE_CONVERTER_INIT   
    Cause: The desired conversion is not supported. (Due to specification of invalid code page or of language not supported in the conversion, with SET LOCALE LANGUAGE.)
    Runtime Error: CONVT_CODEPAGE_INIT
    CX_SY_CONVERSION_CODEPAGE
    Cause: Internal error in the conversion.
    Runtime Error: CONVT_CODEPAGE
    CX_SY_FILE_AUTHORITY
    Cause: No authorization for access to file
    Runtime Error: OPEN_DATASET_NO_AUTHORITY
    Cause: Authorization for access to this file is missing in OPEN DATASET with addition FILTER.
    Runtime Error: OPEN_PIPE_NO_AUTHORITY
      CX_SY_PIPES_NOT_SUPPORTED   
    Cause: The operating system does not support pipes.
    Runtime Error: DATASET_NO_PIPE
    CX_SY_TOO_MANY_FILES
    Cause: Maximum number of open files exceeded.
    Runtime Error: DATASET_TOO_MANY_FILES   Non-Catchable Exceptions   
    Cause: An attempt was made to open a pipe that is already open.
    Runtime Error: DATASET_PIPE_POSITION
    Hope that will help you.
    Please reward if useful.

  • In the Extended Classic scenario, what creates the PO on the SRM side?

    Hi Experts,
    This sounds like a simple question, however, I've been unable to find the answer.
    What I am looking for is the process (report, workflow or function module etc etc) that actually creates the PO on the SRM side once the shopping cart has been approved (before it is replicated to ECC).
    The reason for this is, after a support stack upgrade, the creation of the PO seems to have slowed down once the shopping cart has been created.  I'm trying to track down where the PO gets created and what triggers that to happen, in order to work out why it isn't as quick as it was prior to the upgrade, but can't piece together the full end to end process.
    I can see the "Workflow Without Approval Shopping Cart" workflow that obviously Releases the shopping cart and sets the status to Approved...  I can then see the equivalent workflow for the PO (Workflow Without Approval for PurchOrder), but I can't work out the bit inbetween -
    - How does the PO actually gets created in SRM and what triggers that to happen?
    Any help will be gratefully received - thanks in advance.

    its an event related to the shopping cart business object- BUS2121.
    your approval workflow should be of status set released, which will trigger the methor BBP_REQREQ_TRANSFER, finished approval is the event which will be triggered by the workflow, based on this event, system will trigger reqreq_transfer.

Maybe you are looking for