Skip to Content
avatar image
Former Member

Extended classic scenario - no backend PO created

I try to activate the extended classic scenario. It's not activated in customizing, tried to do it only with BADI implementation for special material groups. We are able to create POs in SRM but transfer to backend doesn't work.

I get following error messages in application monitor as backend application errors:

No instance of object type PurchaseOrder has been created. External reference:

PO header data still faulty

Document number 100000093 not within defined inter val

What's going wrong here?

Hubert

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Best Answer
    Jul 19, 2010 at 11:53 PM

    Hello,

    Check if you have set up the customizing as below:

    Extended classic scenario:

    a) at SRM side:

    - To assign the transaction type to the extended classic scenario you have to maintain the transaction type name (= the R/3 PO document type) to the attribute DP_PROC_TY (in contradiction to BSA in classic scenario) in PPOMA_BBP of the responsible Purchazing group.

    - Create a number range for a local PO.

    - Assign the local PO number range as a internal numer range to the transaction type.

    b) at R/3 side:

    - Enter the Number Range (corresponding to the SRM number range PO) and flag it as an external number range (trx. OMH6 Number Range for Purchasing Documents)

    - Maintain the document type corresponding to the SRM transaction type and assign the R/3 number range for POs as "NoRge Ext" (field V_T161-NUMKE) (trx. Document type within Purchase Order Customizing)

    - Make sure that the SRM and R/3 number ranges match are exactly the same.

    Kind regards,

    Ricardo

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jul 20, 2010 at 03:05 AM

    For information .

    In classic scenario:

    a) at SRM side:

    SPRO activity "Define Transaction Types":

    - The name of SRM transaction type corresponds to the same name of the

    document type on R/3 side.

    - To assign the transaction type to the classic scenario you have to

    maintain the transaction type name (= the R/3 PO document type) to the

    attribute BSA in PPOMA_BBP.

    - You must enter the following as interval numbers:

    Exactly the value Int.No. of the shopping cart transaction type that was

    defined in activity Define Transaction Types.

    LO for local purchase orders

    RQ for purchase requisitions in the backend system

    PO for purchase orders in the backend system

    RS for reservations in the backend system

    - These number ranges you can see in SPRO activity "Define Number Ranges

    for Shopping Carts and Follow-on Documents":

    b) at R/3 side:

    - Enter the Number Range (corresponding to the SRM number range PO) and

    flag it as an external number range (trx. OMH6 Number Range for

    Purchasing Documents)

    - Maintain the document type corresponding to the SRM transaction type

    and assign the R/3 number range for POs as "NoRge Ext" (field

    V_T161-NUMKE) (trx. Document type within Purchase Order Customizing)

    -Make sure that the SRM and R/3 number ranges match are exactly the

    same .

    Regards

    Lauren

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jul 16, 2010 at 01:31 PM

    Did you check the po ?

    Add comment
    10|10000 characters needed characters exceeded

  • Jul 16, 2010 at 01:52 PM

    check number range between both srm and ecc systems.

    since srm is maste rsystem to create numbers for PO bo.

    Add comment
    10|10000 characters needed characters exceeded