Signature capture on mobile device

[Former Member]

HI,

I am looking for some document/white paper on the capability of signature capture on a mobile device when a driver delivers a product to the customer. In addition this signature should be stored in the back end SAP ECC.

Which SAP functionality supports this feature? Any help on this would be appreciated.

Thanks

Ash

[Former Member · Accepted solution]

HI Ashish

Please check this forume link

This link is related to your problem.Hope this link will help you

Regards

Ruturaj

[Former Member]

Hi,

I have netweaver version 7. Would there be any issues if I don't upgrade to version 7.1? What functionality would I loose?

Lastly does the SAP ECC version matter? We are in SAP 4.7

Thanks

Ashish

[Former Member]

Hi Ashish,

Netweaver mobile 7.10 is not just another new version of Netweaver Mobile 7.0

Mobile 7.10 comes with a complete architectural change and has more capabilities compared to 7.0 , high scalability(data volume, number of devices etc) , better modeling options, multi channel access to name a few.

If you are planning for developing a new mobile application , its recommended to start with NW Mobile 7.10

As far as I understand , there is no tight coupling to SAP ECC version for mobilizing applications using DOE.

DOE talks to Backend via bapi wrappers (getlist, getdetail,create, modify , delete) . Hence only criteria would be these bapi wrappers which handles data persistency and retrieval in backend tables to be made available for DOE to invoke .

Regards,

Liji

[Former Member]

What is effort involved in upgrading from 7.0 to 7.10? Is it a big change? Any time estimate would be great.

Also what is the typical implementation time frame for an implementation for developing a mobile application for signature capture? I am just looking for a ballpark estimate.

[Former Member]

Any examples of signature capture devices that you may have used

[Former Member]

If you have a mobile application up and running on netweaver mobile 7.0 , then upgrade path to NW mobile 7.10 is a two box upgrade and migration path exists for the application and devices connecting to old server...

Check the migration doc link [Migration Doc|https://websmp107.sap-ag.de/migrationNWmobile71]

In other cases since Mobile 7.10 will be part of the Netweaver ABAP AS installation and if you are able to upgrade your current box to Netweaver ABAP AS 7.10 , then you will get DOE also part of it as there is not seperate installable unit for mobile.

APP development time is dependent on many factors like complexity of the application itself(number of data objects involved , kind of distribution criteria required , the actual app (client UI) development ,availability of backend bapi wrappers.etc etc.) a very simple test app could be developed well with in a week's time and We recently heard about a pretty complex app developed with in 2 months using DOE and standard SAP client framework. Very hard to generalise I would say..

Regards,

Liji

[Former Member]

What is the time and effort to change an already deployed mobile application? E.g. add another field etc

[Former Member]

Hi Ashish,

If you are talking about changing the mobile application which is deployed on 7.10, then the efforts are very minimal.

Its just adding the necessary attributes in the corresponding data object, do the model import in the NWDS and develop application again.

Additionally, you can upload this application on the DOE server and do "Server Deployment" for all the devices which want this upgraded application.

Regards,

Ramanath.

[Former Member]

What is the process of adding devices in a working mobile application? Is just that the device have to subscribe to the application?

Also what is the deployment method for a modified mobile application in addition to DOE server deployment? How exactly does server deployment work and other methods work?

[Former Member]

Hi,

If the application is uploaded to the DOE server, then you can go to "Mobile Component Administration" and add devices to this MCD(application).

This will make sure that the necessary application archives are sent to those devices and after syncrhonization with the DOE server, these applications will get installed on those devices.

Server deployment is the best way to achieve the application upgrade as it takes care of sending only the "Delta Data" due to the application upgrade. When you assign a newer version of the mobile application to the device, it will flow down to the device during synchronization.

Client framework would automatically un-install the older version and install the newer version of the application. after successful installation, DOE will send the "Necessary" data if any to the client.

Regards,

Ramanath.

[Former Member]

Hi Ramnath,

Thanks for your help. Do you mind sharing your email address.

Thanks

Ashish

[Former Member]

Hi Ashish,

Sharing an email id would not feasible option here because the responses to your queries would be restricted to me only. Instead if you keep on posting your doubts/queries here, the probablity of getting quick responses increases.

Let us know if you are facing any problems during the development and we will try to resolve it asap.

Regards,

Ramanath.

[Former Member]

Does anybody have a high level architecture diagram? A high level powerpoint will also be great

[Former Member]

Hi Ashish,

look at this e-learning stuff..checkout the third slide about architecture

[e-learning mobile|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/204fc387-6646-2a10-99b7-bba030bc3f68]

Regards,

Liji

[Former Member]

Also how do I present information on the signature capture device which could potentially have customer name, delivery number or order number etc and signature?

Does SAP provide standard templates that can be used.

[Former Member]

Hi Ashish,

The information like customer name, delivery number can be captured in the attributes of the data object.

Data object is an entity that can be defined in DOE using SDOE_WB transaction.

This data object can have the custom defined fields as per the requirement of the application and these attributes can be used on the mobile device to communicate this information to the DOE as well as backend system.

Regards,

Ramanath.

[Former Member]

Hi Ashish,

All these details can be presented in a mobile application that runs on the mobile device .Netweaver mobile constitutes of server (DOE) and a default client framework (Netweaver mobile client) . A mobile application could be created using NetweaverDeveloper Studio(NWDS) that will present the data required by the mobile device user.

This mobile application once deployed on a device will work on the local persistency and during synchronization with DOE sends the modified/new data to Backend via DOE.

Customers can also develop a custom client framework and application that still talks to DOE (and inturn to backend)

During the design time activity of modeling business objects (called data objects in DOE) corresponding to the backend objects , all the fields to be presented to the mobile user (the relevant fields that a mobile application uses) have to be made as data object attributes. This data will be populated to DOE from backend via bapiwrappers.

DOE will send this data to the application on the mobile device using a messaging protocol over http connection.

This application can be built according to the customer's requirement depending on the business use case of what kind of data need to mobilized.

check this link [Develpers guide|http://help.sap.com/saphelp_nwmobile71/helpdata/en/8F/0B674240449C60E10000000A1550B0/frameset.htm]

Regards,

Liji

[Former Member]

Hi Ashish,

Netweaver mobile 7.1 (DOE & mobile client) has capabilities to act has a middleware between backend and mobile device performing data distribution where applications could be built and deployed to mobile devices.

Refer to this link to know more about occassionality connected application with NWmobile 7.1

[Link 1|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/204fc387-6646-2a10-99b7-bba030bc3f68]

DOE has capabilities to transfer attachments from / to mobile application from / to backend.

Check for a signature capture tool. Most of the phones come with their own signature capture tools , for eg. for Pocket PC capture program can be downloaded from MSDN site .Store the captured signature as an JGP/ PDF/ or any version.

Convert this file into binary format in the mobile application and upload this attachment in binary format to DOE and inturn it will get persisted in backend.

DOE exchanges data between backend via bapiwrappers / RFC enabled FMs.

The signatures have to be stored as attachements in the DOE and the backend. check out the following link for attachement support

[attachments in DOE|https://www.sdn.sap.com/irj/scn/wiki?path=/display/mobile/createapplicationsusingBinaryMemoandTextMemoinNetweaverMobile+7.1]

[uploading attachments|https://wiki.sdn.sap.com/wiki/display/mobile/Uploading%20Attachments-%20Netweaver%20Mobile%207.1]

This thread might also be useful

[]

Regards,

Liji

[Former Member]

Hi Ashish,

You can use NetWeaver Mobile 7.1 (DOE) to achive this functionality. It has attachment support functionality which can be used to capture the signature on the mobile devices and then upload it to the backend ECC servers.

In this case, the signatures will be saved as BLOB field and uploaded to the backend using the bapi wrappers.

Regards,

Ramanath.

[Former Member]

Hi,

For more details, you can also refer to this blog.

/people/katja.schuchardt/blog/2009/07/27/sap-netweaver-mobile-71--transfer-of-files-using-attachments

Regards,

Ramanath.