on 06-04-2014 9:46 PM
When a service item is passed from an external catalog, how is the Delivery Date range captured in SRM?
Is the delivery date's passed in the Long Description and then SRM pulls it from there? Is this standard?
From what I can see, currently the only value passed that has to do with delivery is NEW_ITEM-LEADTIME[n] but this just has a lead time in days, but no actual date range.
Thank you,
Andrew
Hello Andrew,
here is the ABAP code concerning SC delivery date for good or timeframe for service.
IF NOT cs_sc_item_data-leadtime IS INITIAL.
cs_sc_item_data-deliv_date = sy-datlo + cs_sc_item_data-leadtime.
ELSE.
cs_sc_item_data-deliv_date = sy-datlo.
ENDIF.
* fill performance period for services
IF cs_sc_item_data-product_type = c_ptype_service.
cs_sc_item_data-vper_start = cs_sc_item_data-deliv_date.
ENDIF.
This is FORM create_sc_item_data from BBP_WS_IMPORT_SC_DATA function module.
Regards.
Laurent.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the Reply Laurent.
I'm not very technical, but from what I understand above it looks like the system has a way of figuring out the range using that cs_sc_item_data-leadtime value, and it has a way to figure out the start time of the service using sy-datlo?
Is this a standard solution within SRM? Do current companies use the standard OCI interface to purchase services including a valid delivery date range?
Regards,
Andrew
Hello Andrew,
Andrew Bondarev wrote:
(...)
Is this a standard solution within SRM?
(...)
Yes.
Andrew Bondarev wrote:
(...)
Do current companies use the standard OCI interface to purchase services including a valid delivery date range?
(...)
Never seen customer using catalog for services.
But SRM standard allows it.
Regards.
Laurent.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.