ASN in Extended Classic Scenario with SUS

Hi SRMer?
Is it possible to create an ASN in SUS with Extended Classic Scenario (ECS)?
OSS note 543544 mention that the scenario is limited for document types Purchase Order, Purchase Order Response and Change Order. Confirmations and invoices are not possible. There is no indication on ASNs.
Any help will be appreciated.
Regards.

Hi
Please go through these links ->
SUS-MM Confirmation without ASN
Re: Details on ASN
The specified item was not found.
SUS ASN - mandatory field
ASN Confirmation not created,
Clarifications on EBP-SUS and MM-SUS Scenario
Re: SUS-MM scenario with "POR (order ack.)" and ASN for free text
Creating custom field in ASN screen of SRM SUS
SUS Invoice
Regards
- Atul

Similar Messages

ASN for extended classic scenario

Hello all,
we have SRM with extended classic scenario (EBP-MM),
is it possible to use ASN (shipping notification) functionality in our system ?
Kind regards,
Arthur

Hi
ASN can be created by the vendor in SUS system for that XI mapping is required. ASn can be created in SUS by any vendor users. I guess it's not possible with ECS.
Please check the SAP Consulting Note 1026638 GR Output Integration with MM-SUS Scenario for R/3 <= 47
You need to have functional background for this:
To create an ASN against PO or SA release:
1. you need to compulsarily put how much qty you are sending against the reqd. qty(shown by PO / SA )
2. dispatch vehicle no. (optional)
3. road challan no. (optional)
4. one more optional entry ( sorry I forgot)
Useful related pointers ->
Re: how does the GR get into SUS---MM-SUS Sceanario
ASN in Extended Classic Scenario with SUS
SUS ASN & Invoice
The specified item was not found.
Do let me know.
Regards
- Atul

Can we use the Extended Classic Scenario with MM-SUS

HI, expert :
    In extended classic scenario ,the PO created in SRM system ,and then replicated into the MM system .You can't change it in MM system .
    So, in this situation ,I want to know the MM-SUS can be suitable or not ?The PO can transfer from ECC to SUS ?
   If I use the decoupled scenario ,which one I can select ?MM-SUS or EBP -sus ?
   BR !
Alex!

Hi Alex,
as noted by Bill, in MM-SUS is the extended classic not possible at all.
By default it's also not supported in the SRM-SUS. Please see the note 543544. If you would like to activate this, you need to pay a consulting fee for SAP:
"Please note that the full scenario can be enabled by a consulting solution, compare OSS note 700350."
Regards,
Peter

Classic and extended classic scenario with one EBP

Hello Guys
If I have a one EBP and multiple ERP back ends. For one backend, I need to have classic and other to have extended classic scenario. How this can be fulfilled. Is it possible, if so please provide the configuration setup.
Thanks in advance.

Hello,
In BADI BBP_EXTLOCALPO_BADI method DETERMINE_EXTPO.
you can try this.
Structure Declaration
DATA: ls_item_data TYPE bbps_extpo_badi.
Moving item data to a structure
MOVE-CORRESPONDING item_data TO ls_item_data.
SELECT SINGLE LOGSYS FROM comm_product
                                 INTO lv_logsys
                                 WHERE PRODUCT_GUID = ls_item_data-PRODUCT .
If lv_logsys = 'XXXCLNT010' "backend system
      Cancelling the enhanced classical scenario
        bbp_extpo_gl-bbpexpo = space.
ELSE IF lv_logsys = 'YYYCLNT010' "backend system
      Cancelling the enhanced classical scenario
        bbp_extpo_gl-bbpexpo = ' X'.
ENDIF.
Regards,
Neelima

PO output for Extended classic Scenario from the R/3 backend

Hi,
1) Does the PO output (ignoring the config maintained in SRM server 5.5 for the output) through R/3 backend is standard or it is mandatory to give local outputs from SRM only incase of Extended classic scenario?
Regards,
DV

Hi Anil,
We are working on extended classic scenario with SRM 5.0 & ECC6.0.
Please explain how we can take "PO output for Extended classic Scenario from the R/3 backend ".
Please send the related document to [email protected]
Thanks in advance
Ashutosh

Extended Classic Scenario - Free Items?

Does SAP support PO's in Extended Classic Scenario with a zero price (free items)?
My client is switching from classic to extended classic scenario and they require to be able to creaet PO's that have a zero price like they have in the classic scenario.
We are currently getting an error that we need a price with the IR flag, but I would expect the system to automatically unflag the IR flag for a free item?

Hi Jay,
Thanks for your response. There are two problems with your soluiton. First the shopping cart doesn't have the IR flag on it and can't be changed by the user and we have PO's created directly from SC's and go out to the vendor.
Second, In extended classic scenario it apprears that the system doesn't allow you to change the ir flag on the PO and make the cooresponding change in the ERP PO.

Completion workflow in extended classic scenario

Hi gurus,
We use extended classic scenario with SRM Server 5.5.
In ppoma, each purch org and purch groups has the local and the backend. Vendors are replicated to backend purch org and then also to the local purch org.
I have seen that in classic scenario purchasers should be assigned to the local purch org. however, completion workflow only determine the agent (purchaser) if it is in the backend purch org.
The problem is that then this purchasers cannot manage any business partner.
How can I solve it?
I have seen other clients that the completion workflow determine the agents in the local purch org...
Many thanks!!!
Regards
Patrícia

Hi,
In the Extended classic scenario, local purchasing organisation and purchasing groups are required to create shopping carts and purchase orders. in this scenario, when
the vendors are replicated from the SAP back-end using BBPGETVD,BBPUPDVD program or vendor-synchronization programs, the vendor update in SRM is only for the R/3 purchasing organizations. because the local purchasing organisations are required in SRM for the Extended Classic or standalone scenario, these replicated vendors needs to be extended to the local purchasing organisations.
organizations can use Tx. BBP_UPDATE_PORG for extending the vendors to the local purchasing organiztion.
see OSS Note 390546 for more info.
Regards
vasanth

Material PO confirmation at supplier side (SUS) not taking place in SRM SUS Extended classic scenario

We have configured extended classic scenario SRM with SUS, and all functions are working fine. However, at the time of PO confirmation of material item at the Supplier side (SUS), the material line item disappears when we click on the Create Confirmation button in SUS. The functionality is working fine for Service Items. The total value of PO is also displayed correctly in the Items overview section.
Please provide some help in solving this issue.

Hello,
This is the correct behaviour of SUS - confirmations can only be created for service items which in turn create service entry sheets (Trx: ML81N in ECC). And accepting the SES in ML81N will generate GR posting.
For material items, you have to create ASN which will in turn create inbound delivery in ECC which you can post and will generate goods movement documents.
So basically, for service items you create confirmation and for materials you create ASN.
Regards,
Prasanna

Use the MM-SUS in Extended Classic Scenario

HI,my experts :
    The standard function doesn't support the MM-SUS in Extended Classic Scenario .Now I may have two questions about it .
1、 I have one ECC system .I need handle the invice in the ECC system .In other word ,the invoice rcreated in the SUS should transfer to the MM system .But in EBP-SUS ,the invoice is transfered to the SRM system .What can I do now ?
2、 If I want to use the decoupled scenario ,some POs are create in EBP ,and others are created in MM .Now ,which sus I should select ? EBP-SUS or MM-SUS?
   Or some detail document about it .
BR!
   Alex!
Edited by: Alex on May 25, 2010 9:17 AM

Khan has explained most of the things.
The external web service I meant is actually OPI catalog which you need to maintain.
The same has to be entered in the attribute CAT of the EBP purchaser.
To maintain the call structure of this catalog
Get the URL from SE80->BSP appln->ros_prescreen->controller->main.do
then give the client no of yr ROS client
the RFC user user ID from EBP to ROS
it's password
sap-sessioncmd=open
sap-language=sy-langu
the operational purchaser role in EBP (sap_EC_BBP_OP_PURCHASER) should be linked with
the same in ROS via role menu->business partner->screen supplier->right click->change details
->sap-client=ROS client no
The administrator & op purchaser should be present in ROS org structure also
& should have same userID & password as EBP
you have to define the vendor root, the root of the purchasing organization and the currency in
table BBP_MARKETP_INFO in the SRM System (Enterprise Buyer client).
BR
Dinesh

SUS-MM vs SUS-EBP (Extended CLassic Scenario)

Hi!
We have an extended classic scenario already up and running between ERP->EBP system without XI usage.
Now it is necessary to configure SUS integration for ASN creation purpose. As I can see SAP has 2 standard configuration guides: one for SUS-MM and another one for SUS-EBP, but they are not fully relevant for ECS.
Could anybody tell me please from what system EBP or ERP it is better to send PO to SUS system when we are using extended classic scenario? And what are advantages/disadvantages of this?
Thanks and Regards,
Siarhei

Hi Dinesh!
Thank you for your answer! It is clear that leading PO is in EBP, but why I can't use ORDERS and ORDCHG IDOCs to transfer PO and PO chnages to SUS?
One other question: do you know whether Configuration Guide for ECS exsits (like SUS-MM and SUS-EBP documents)?
BR,
SIarhei
Edited by: Siarhei Tsikhanenka on Apr 4, 2008 9:56 AM

SAP eSourcing with SRM Extended Classic Scenario

Hi Team,
We are using ECC 6.0 with eSourcing. Currently we use SRM 5.0 with Classic Scenario.
Now we are planning an upgrade from SRM 5.5 to SRM 7.0 and want to do the Extended Classic Scenario. This will help us to do additional functionalities of SRM.
eSourcing can be used for Strategic RFx and CLM functionalities.
SRM can be used for SC, Operational Sourcing and PO. We can also use the SRM-SUS Scenario for PO confirmation and Invoices.
Have any one used eSourcing with SRM Extended Classic? In that case, please provide some light into how to use all these application to better streamline the overall Source to Procure strategy.
Also, do you think Classic is the way to go or Extended Classic is better? Any documents or pictures are greatly appreciated.
Thanks
Jogy

Hi
SAP provide standard integration b/w ECC and Esourcing/ CLM (PR (both inbound and outbound). However in case you decide to go with extended classic scenario,you might need e Sourcing/ CLM integration with SRM (since PO would be created in SRM) which is not provided out of the box by SAP. However custom interface (based on flat file transfer) can be built b/w SAP SRM and e Sourcing.
MM-SUS scenario is not much different from EBP-SUS scenario in terms of functionality.
Regards
Mudit Saini

Payment term key with limit days in Extended Classic Scenario

Hello,
We have an SRM 4.0 implementation (SRM Server 5.0 with Support Package
9) using the Extended Classic Scenario.
When a shopping cart is created, it must be approved, and then a
purchase order is generated (first locally at SRM, and then is
replicated to the backend).
The problem is that the payment term key (field at header level EKKO-
ZTERM) of the backend purchase order is empty, only in cases when we use a payment term key which have several different values for the
field "limit days" (T052-ZTAGG in backend, BBP_PAYTERM-ZTAGG in SRM).
Example:
     ZTERM     ZTAGG
      K180           09
      K180           19
      K180           31
If the payment term key selected has no several values for the field "limit
days" (one single entry), the payment term key arrives correctly at the backend purchase order.
Example:
     ZTERM     ZTAGG
      E000           00
In SRM table BBP_PAYTERM we have upload the backend payment terms
(using report BBP_UPLOAD_PAYMENT_TERMS). In other threads it is said that you must copy the entries generated by the report with the logical system of the SRM system, but in extended classic scenario it seems to be not necessary.
We have already implemented note 846009, in order to use always the backend payment term, but the error didnt get resolved.
We have our vendor business partners mapped to the local and backend
purchasing organizations, but it is only necessary indicate the Payment term key for the Backend Purchasing Organization.
Regards

hi,
Pls see the foll notes:
Note 576349 - Terms of payment in the ECS
Note 541934 - Modification note: Copying base date from T052
Note 953999 - ECS: Terms of Payment values not in PO header
<b>Note 940453 - Backend payment term data not updated in the extended PO
Note 945018 - Incoterms data not transferred to the back end</b>
BR,
Disha.
Pls reward points for useful answers.

'BAPI_POEC_CREATE' function doesn't work with extended classic scenario

Hi everybody.
Antecedents:
We are working in an extended classic scenario.
When we create a Purchase Order via ITS in SRM, the system works ok, the PO is replicated in the ERP system.
But when we execute BAPI_POEC_CREATE function module in order to create a PO in SRM, no message are available in the application monitor, but the PO is not replicated in the ERP system.
Both exampled were created with exactly same data (partners, items, categories, accounts, )
Moreover when we modify the second PO created via ITS, the systems doesnt show any error message, we can order our PO again without error, but the PO isnt replicate in the ERP system.
1. We executed BAPI_POEC_GETDETAIL function module, and there is only a difference between POs, E_PO_STATUS table.
PO created by transaction has 8 entries:
       I1009 X
       I1015 X
       I1021
       I1038
       I1039 X
       I1043
       I1080 X
       I1180
And PO created by BAPI has 5 entries:
       I1015 X
       I1021
       I1038
       I1043
       I1180
2. We run BBP_PD transaction, and there is only a difference.
PO created by transaction mode shows:
- Message: W BBP_PD 830 Default values have been taken from Vendor PRUEBA10/purchasing organization Área Global Compras (org. compras)
And PO created by BAPI
- Message: No Messages
Could anyone help me with the problem?
Thanks in advance.
Raúl.

Hi Raúl,
this is exact, BAPI_POEC_CREATE is designed to create local PO.
If you want to replicate it to R/3, then you have to change it to an ECS PO.
In BADI BBP_DOC_CHANGE_BADI, called at the real beginning of BBP_PD_PO_CREATE, you will have to change some data to enable the ECS scenario:
- change header subtype to EP
- change header log system to SRM (keep FI LS as is)
- determine a backend purch group & org
- complete BE fields (be_object_id, be_object_type, don't change be_log_system because it will be determined during the transfer, be_pur_org and be_pur_group will also be determined during the transfer)
- ... and maybe other R/3 relevant fields
Compare both PO one by one, and adapt the gaps.
Rgds
Christophe
PS: please reward points for helpfull answers

SUS / no goods receipt doc to backend in extended classic scenario?

Hello
have you any find a solution for problem
in SRM/SUS and goods receipt in extended classic scenario. Gr remains only in SRM not going to backend...
Brg Harri
Message was edited by: Harri Harkonen
Message was edited by: Harri Harkonen

Hi Christophe,
We also have this issue. Goods Receipt from SUS is created in SRM but is not posted in backend (we have implemented extended classic scenario).
I tried to use the BBP_DOC_SAVE_BADI to created an idoc which posts the material document in backend system (using fm IDOC_GR_CREATE).
The goods receipt is posted in backend this way.
Unfortunately we are not able to cancel or make a return delivery on this GR.
I am very interest in your FM. Could you please share this, or tell me what changes you made to the GR in SRM.
Thanks in advance.
Rgds,
Martijn

SC with Limit Item using Extended Classic Scenario?

Hello,
Can we implement SC with Limit Item using Extended Classic Scenario.
I mention that we replicate the Product Categories from R/3 backend.
We have tried to create a SC with Limit item, but the data on Quantity, Price and Tax is not picked up at PO level.
Regards,
Shaiek

Hi
Please try out this.
For the time-being,
Try de-activating all the custom BADI Implementations and check, what is happening, in the standard SRM system. How does it behave incase of limit item ?
Incase it works fine, without any Custom Implementation active in the system, I suspect there is something wrong in your current deactivated BADI Implementation.
Since i don't have access to your system , Please paste the code here.
Hope this will help.
Please reward suitable points.
Regards
- Atul

ASN in Extended Classic Scenario with SUS

Similar Messages

Maybe you are looking for