sapnote_0000755712

27.06.2011 of 9

SAP Note 755712 - Release restrictions/information forDSD

Note Language: English Version: 40 Validity: Valid Since 24.08.2009

Summary

Symptom

This note contains release restrictions and additional information aboutinstalling and using Direct Store Delivery (DSD) in ERP 2004, ERP 6.0(former ERP 2005), ERP 6.0 Enhancement Package 3 (EhP3), and ERP 6.0Enhancement Package 4 (EhP4).

Other terms

Direct Store Delivery, Mobile DSD, ME, MI, NetWeaver, NetWeaver Mobile,prerequisites, release restrictions

Reason and Prerequisites

CAUTION: This note is constantly updated. You should ensure that you arereading the most recent version.The following information corresponds to the last date that this note waschanged.

Solution

Glossary:

o DSD = Direct Store Delivery

o DSD backend = DSD function in ERP without a mobile deviceconnection

o DSD scenario = DSD backend in conjunction with xMDSD

o Mobile DSD (MDSD) = DSD component for the mobile device connection

o Mobile Infrastructure = NetWeaver component for integrating mobileapplications

Software release restrictions

o Direct Store Delivery (DSD) is specific to the consumer productsindustry and expects an ERP standard implementation. Pleaseconsider that the problem-free use of DSD in combination with otherindustry solutions or add-ons is not guaranteed. Therefore any ofthese combinations has to be tested on a project basis prior touse.

o xMDSD 2.1 is released for ERP 2004 with Stack 14 and for ERP 6.0with Stack 06.

o MDSD 3.0 is released for ERP 6.0 EhP3.

27.06.2011 of 9


o MDSD 4.0 is released for Ramp-up with ERP 6.0 EhP4 since August24th 2009.

o For using Truck Stock Visibility functionality in correlation withexcise duties, please be aware that legal requirements regardingtax warehouses, tax relevant material movements etc. have to beconsidered during implementation.

Functional restrictionsPlease consider that some of the following restrictions are resolved withERP 6.0 EhP3.

o All mobile devices that are connected to an ERP system work in justone language.The DSD connector can handle only texts for one language. If thematerial master data are maintained in multiple languages it isnecessary to filter the material master text for the desiredlanguage within the ALE customizing.Resolved with ERP 6.0 EhP3.

o You can create return requests and deliveries, as well as freerequests and deliveries, on the mobile device as an additionalactivity. However, in the Final Settlement Run, the return itemsare dealt with as normal returns and the free items are dealt withas normal order items. You can define a differentiated customersales transaction type determination (BADI /DSD/SL_FSR_DEFFMT_P)using a customer-specific implementation for thebadi_determine_cstatyp method. You can use this implementation tofind an alternative sales returns transaction type (customer salestransaction type). In addition, you can adapt the execution of thenewly found customer sales transaction types.The control parameters used in the backend do not appear on themobile device.

o If a customer receives more than one invoice document on a tour,you must print all of these invoice documents in the same way:Either print all documents on the mobile device or do not print anyof these documents.

o If invoices that were created on a mobile device are reprinted inthe DSD backend, a note regarding the repeat print is missing onthe print output.Resolved with ERP 6.0 EhP3.

o Only one subset unit is supported on the mobile devices. Forexample: Base unit of measure = box (20 bottles), subset unit =bottle.

o When determining the available credit limit, the system currentlyonly accounts for the open items for the company code to which thedriver is assigned.

o DSD Visit Control is not taken into account in the sales order inCustomer Relationship Management (CRM). If you use CRM CIC(Customer Interaction Center) for DSD processes, it is stillpossible to create the sales order directly in the R/3 system from

27.06.2011 of 9


CIC.

o The call frequencies of the call list in CRM CIC are notsynchronized by default with Visit Control in DSD (visit lists).

o Non-cash payment types (e.g. credit card) are handled within DSD asa cash payment type. This means that the open items will be clearedduring the Final Settlement Run, the customer will be credited evenwithout the payment receipt.Resolved with ERP 6.0 EhP3.

o It is not feasible to download documents for CPD customers frombackend to front-end because no address data for CPD customers aredownloaded to the mobile device. Therefore CPD customers can onlybe used to create documents on the mobile device and can beuploaded to the backend.

o Mobile and Paperbased Process

- Manual header conditions are not calculated correctly in case adelivery split is used.

- A pricing procedure which includes scales cannot be used for adelivery driver process.

o Mobile Process

- In case of a combined mobile process (preseller and deliverydriver) the mobile DSD Manual Discounts and the mobile DSD DealConditions are only to be used in the delivery process.

- Manual changes in the pricing of the order in the backend arenot allowed.

o Paperbased Process

- In case of a combined mobile process (preseller and deliverydriver) it is not possible to change or delete the mobile DSDManual Discounts and the mobile DSD Deal Conditions which werecreated by the preseller. The delivery driver is only able toadd conditions.

o In a delivery driver scenario presold empties are not reserved andcan be sold to other customers without warning.

o The 'Batch management', 'Split valuation' and 'Handling UnitManagement' functions are not supported in DSD.

o The 'Change Pointer' functions are not supported in DSD.

o The 'Status Management' functions are not supported in DSD.

o If the DSD/ERP system is connected to a CRM system, it is notrecommended to switch-on the CRM scenario "A" (Cross System Lock)because this may possibly result in lock situations during DSDfinal settlement run.

27.06.2011 of 9


o During maintenance of DSD Deal Conditions in ERP potential limitsof the related condition type are not checked.

o The Direct Store Delivery Solution is not released for processesinvolving more than one delivering plant, in particular in the areaof reload and truck to truck transfer scenarios. Therefore SAP cannot guarantee that DSD processes involving more than one deliveringplant are working properly and strongly recommends careful testingon a project basis in this case.

Country versions

o The DSD scenario is released for the following countries:Austria, Australia/New Zealand, Germany, Great Britain, Poland,Portugal, South Africa and Venezuela.

o The DSD scenario is released with the specified restrictions forthe following countries:

Switzerland:

- The inpayment slip with reference number is not supported.

Spain:

- The tax exemption number is not supported.

- The indicator for sales equalization taxes in the case of asales tax exemption is not supported.

o The DSD scenario is released for Canada, Mexico and USA as of ERP6.0 Stack 06. For more detailed information, please see note976725.

o The DSD scenario is released as of ERP 6.0 Stack 06 for thefollowing countries with the specified restrictions:

Belgium:

- Sequential Document Numbering

- Invoice reference to prior outgoing documents

Czech Republic:

- Rounding for VAT calculation

China:

- VAT invoice creation on the mobile device

- Special consumption tax (excise duty)

Chile:

- Document NumberingVoiding of official document numbers in case of re-print or

27.06.2011 of 9


issues with the paper forms

- Billing Document split

- Withholding tax

Finland:

- Nordic Payment Reference

France:


Indonesia:

- VAT invoice creation on the mobile device

Italy:


- The collection of sales tax only when a specific value for allinvoices in a year has been reached is not supported.

Norway:

- The calculation of the key for the payment reference is notsupported.

- There is no Norwegian language version.

South Korea:

- Tax Invoice Creation

Sweden:

- Nordic Payment Reference

Turkey:

- Amount in words on invoice

- Printed delivery Note for unsold goods

- Special consumption tax (excise duty)

o The DSD backend function is limited to the following countries:Australia/New Zealand, Austria, Belgium, Canada, Czech Republic,Denmark, Germany, Finland, France, Great Britain, Hungary, Italy,Luxembourg, Mexico, Netherlands, Norway, Poland, Portugal, Russia,Singapore, Spain, South Africa, Sweden, Switzerland, USA andVenezuela.

Language versions

27.06.2011 of 9


o The DSD scenario is available in the following languages:Croatian, Czech, Danish, Dutch, English, Finnish, French, German,Greek, Hungarian, Italian, Japanese, Polish, Portuguese, Russian,Spanish and Swedish.

o The DSD backend function is available in the following languages:Chinese, Croatian, Czech, Danish, Dutch, English, Finnish, French,German, Greek, Hungarian, Italian, Japanese, Korean, Polish,Portuguese, Russian, Spanish and Swedish.

System requirements and sizing

o The backend system and the connected middleware system must be setidentically with regard to Unicode: Either they are both set asUnicode systems or both are set as non-Unicode systems.Combinations of Unicode and non-Unicode systems are not supported.

o Prerequisites for client systems (mobile devices):Device types: PDAOperating system: PocketPC 2003/PocketPC 2003 SE or laterMinimum RAM: 128 MBDatabase: IBM DB2e

It is strongly recommended to check the list of SAP NetWeaversupported device operating systems and the peripherals (i.e.printers, barcode scanners):

- Operating system at: http://sdn.sap.com -> SAP NetWeaverProduct -> Complementary Offerings -> SAP NetWeaver Mobile ->Product Availability Matrix

- Peripheral Support: Note 761833 (see below)

o For detailed information about sizing of the DSD backend systemplease see SAP note 964301.Detailed information for sizing of Mobile DSD can be found in theSAP Service Marketplace: http://service.sap.com/sizing -> HardwareSizing -> Sizing Guidelines -> Solutions & Platform -> SizingMobile Business Solutions.

System restrictions

o For xMDSD 2.1 and MDSD 3.0 you should not plan to connect more than5,000 mobile devices with MI against one ERP backend system. Thisis because of manageability and adminstration features within MI.In any case the number of mobile devices to be connected via MIagainst one ERP system has to be less than 10,000 devices.A range of more than 5,000 mobile devices (but less than 10,000)might be possible. But to do so you have to get permission of SAP.For that purpose please open an OSS message under the LE-DSDcomponent.

o For xMDSD 2.1, MDSD 3, and MDSD 4.0 the reports are defined to beprinted on a 4-inch printer. Printers which have paper width lessthan 4 inch are not supported.

27.06.2011 of 9


Documentation

o For xMDSD 2.1 and ERP 2004 or ERP 6.0 the updated DSD ScenarioConfiguration Guide is available via OSS note 991489 and the DSDDocumentation via OSS note 972869.

o The ERP 6.0 EhP3 & MDSD 3.0 related version of the ConfigurationContent as of ST-ICO-140, is available in the Solution Manager.

o An updated version of the Configuration Guide for ERP 6.0 EhP4 &MDSD 4.0 is attached to this note. This version of theConfiguration Guide relates to the Configuration Content of theSolution Manager SP20.

o Relevant for the implementation of the Direct Store DeliveryScenarios "Mobile DSD Order to Cash" and "Mobile DSD Van Sales"using the Solution Manager cofiguration content delivered with SP20: When target system IMG nodes are accessed via the relatedprocess configuration entries of the Solution Manager, it may occurthat not the targeted node but the complete IMG structure isdisplayed. The user can still manually navigate to the targetednode.

Header Data

Release Status: Released for CustomerReleased on: 24.08.2009 13:01:21Master Language: EnglishPriority: Correction with high priorityCategory: FAQPrimary Component: LE-DSD Direct Store Delivery

Secondary Components:XAP-MBA-DSD Mobile Direct Store Delivery (SAPxMDSD)

Valid Releases

Software Component Release FromRelease

ToRelease

andSubsequent

EA-APPL 500 500 500

EA-APPL 600 600 600

EA-APPL 603 603 603

Related Notes

27.06.2011 of 9


Number Short Text

1445426 Installation information related to xApp MDSD CDP's

1424669 Release Note for MDSD 3.0 SP02

1364390 Release Restrictions Note for SAP MDSD 4.0

1361893 Display error for numerical data in /DSD/DX_AUDIT

1356313 Considering line item no. when creating assgt no. for item 2

1346514 Consider line item no by creation of assignment item no

1289349 MDSD 3.0 SP01 Patch / Hotfix

1284852 Release Information Note for MDSD 4.0 SP00

1130355 Misleading dialog box in tour data entry

1129417 No Reset of Tour Status after deletion from RADB

1123208 Release Restriction Note for SAP MDSD 3.0 SR00

1111146 Release Restriction Notes for xMDSD 2.1 SR02

1108836 DSD EhP 3 Corrections before first delivery (not for SNOTE)

1108316 DSD EhP3 Vasious source code corrections before first deliv.

1106646 Customizing for Middleware in MDSD3.0

1032365 Release Restriction Note for xMDSD 2.1 SR01

995663 Performance improvement in MDSD 2.1 for invoicing

991489 Updated Config. Guide for DSD Scenarios (ERP 2004/2005)

987312 Composite Note for xMDSD2.1 within ERP2004 SP14

986717 DSD: Procedure for dumps when transferring between HH and CN

977745 Composite Note for xMDSD2.1 within ERP2005 SP06

976725 Countr-dep enhancements for tax determination U.S.A., Mexico

972869 Documentation for Direct Store Delivery (DSD)

970411 Customization in Middleware for mDSD Scenarios

968148 MI Performance Issues: Windows Mobile 5.0 support

965707 SAP Mobile Infrastructure 7.0 SPS09- Composite Note

964301 Sizing DSD

956118 SAP Mobile Infrastructure 2.5 SP18 - Composite Note

929303 ERP 2004 SP Stack 12 (05/2006) Release and Information Note

878104 MDSD: SyncBO Interface Check Issue with ERP2004/BEV Backend

819813 Implementation numbering BAdI without effect

819144 ERP 2004 SR 1 Release and Information Note

817946 Dump during mass data processing of /DSD/HH_CONTROL

811490 BE_DELIVERY is deleted when visits are cancelled

811177 Number of the open item is transferred incorrectly

811077 Determination of differences in the settlement cockpit

810784 MDSD: Admin Console ITS Option Display in Browser

809983 /DSD/HH: IDOC /DSD/HH_CONTROL sent incorrectly

809074 FSR BSTKD with several orders for a customer

808250 Final settlement run, supply of new subitems

807825 Check-out and check-in data is not displayed

804999 CheckIn/Out indicator not filled when you enter manually

803946 SAPSQL_ARRAY_INSERT_DUPREC in the settlement run

775561 Security Guide: SAP Direct Store Delivery

772334 Download of a CrEme-Cab file with permanent license

27.06.2011 of 9


Number Short Text

761833 Delivered Drivers for Peripherals in SAP MI

741821 Release limitations concerning SAP ERP 2004

Attachments

FileType

File Name Language Size

PDF DSD_ConfigGuide_2009_EN.pdf E 1.512 KB

sapnote_0000755712

Documents