FS,TS VD01

URGENTLY REQUIRED FUNCTIONAL SPECIFICATIONS(FIELDS) AND TECHINAL SPECIFICATION (FIELDS) FOR THE TRANSACTION VD01,

hi,
FS stands for "Functional specification" and TS stands for "Technical specification".
You receive FS from functional people, it basically consists of the client requirement.
Based upon the FS tghe technical people prepare the TS.
TS consists of the basic approach in order to meet the FS.
More about Functional specifications:
The Functional Specification describes the features of the desired functionality. It describes the product's features as seen by the stake holders, and contains the data needed for the design and development.
The Functional Specification defines what the functionality will be of a particular area that is to be precise a transaction in SAP terminology.
The functional specification translates the Software Requirements template into a technical description which
a) Ensures that the product feature requirements are correctly understood before moving into the next step, that is technical development process.
b) It provides all the information necessary for the technical consultants to develop the objects.
At the consultant level the functional specs are prepared by functional consultants on any functionality for the purpose of getting the same functionality designed by the technical people as most of the times the functionalities according to the requirements of the clients are not available on ready made basis.
For Technical specifications details refer to the thread below
Re: Technical specification
Regards,
Manish

Similar Messages

Error while creating cust In table T078D, the entry VD01 is missing...

Hi Gurus,
I am new to SAP and have just installed SAP 4.7 on my laptop. While creating customer master, a message displays In table T078D, the entry VD01 is missing, and even for XD01 the same message is displayed. Can you guysplease help me with this?
Thanks
Shiva

Hi,
this looks like some customizing records are missing in your installation.
Table T078D contains the transaction dependant field settings.
This is in relation with customizing transaction OB20
In that table, there should be at least 15 records with the corresponding table key
FD01
FD02
FD03
VD01
VD02
VD03
WR01
WR02
WR03
WR11
WR12
WR13
XD01
XD02
XD03
So, if you don't find why standard customizing records are not part of you installation, you may re-create such records with the above keys.
Please note that all fields that are not part of the key should at least contains '.' character for each digits of each fields.
eg: FAUSA is 40 digits long.
FAUSA = '........................................'
Hope this helps
Regards
Alain

Customer master creation(VD01)

Hi all,
As soon as we create an Customer by using VD01 or VD02 it goes into general data.
But in this transaction we have 3 views General data , Company code data and Sales area data.
Here how can I differenciate between this 3 views, ie if i create a custoemr it automatically goes to general data view here how can i find it is in general data view.
My requirement is i need to block creation of general data views for some set of users and for some set of users i need to allow them for Company code data view.
regards,
Smitha Saran

Hi,
your requirement seems related to an authorization customizing.
General data maintenance is protected by authorisation object F_KNA1_GEN
Company code is protected by authorisation object F_KNA1_BUK
and Sales area is protected by authorisation object V_KNA1_VKO
I guess, if the users that tdo not have general data maintenance could have F_KNA1_GEN display only authorisation (03).
Hope this helps
BR
Alain

BDC code for the XD01 and VD01

Hello Masters,
I am new to SAP-ABAP,could anyone help me to get the BDC code to update the customer master data by using the t.code XD01 and VD01.
Thanks
Varsha.

       SESSION METHOD
report YARINSESSIONBDC2 no standard page heading line-size 255.
data: bdcdata like bdcdata occurs 0 with header line.
data: session like apqi-groupid value 'yar1'.
data: begin of itab occurs 0,
      kunnr like lfa1-kunnr,
      name1 like lfa1-name1,
      pstlz like lfa1-pstlz,
      end of itab.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
   FILENAME                        = 'D:\naser.txt'
   FILETYPE                        = 'ASC'
   HAS_FIELD_SEPARATOR             = '|'
HEADER_LENGTH                  = 0
READ_BY_LINE                  = 'X'
IMPORTING
FILELENGTH                    =
HEADER                        =
TABLES
    DATA_TAB                       = itab
EXCEPTIONS
FILE_OPEN_ERROR               = 1
FILE_READ_ERROR               = 2
NO_BATCH                      = 3
GUI_REFUSE_FILETRANSFER       = 4
INVALID_TYPE                  = 5
NO_AUTHORITY                  = 6
UNKNOWN_ERROR                 = 7
BAD_DATA_FORMAT               = 8
HEADER_NOT_ALLOWED            = 9
SEPARATOR_NOT_ALLOWED         = 10
HEADER_TOO_LONG               = 11
UNKNOWN_DP_ERROR              = 12
ACCESS_DENIED                 = 13
DP_OUT_OF_MEMORY              = 14
DISK_FULL                     = 15
DP_TIMEOUT                    = 16
OTHERS                        = 17
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
start-of-selection.
CALL FUNCTION 'BDC_OPEN_GROUP'
EXPORTING
   CLIENT                     = SY-MANDT
DEST                      = FILLER8
   GROUP                      = SESSION
HOLDDATE                  = FILLER8
KEEP                      = FILLER1
   USER                       = SY-UNAME
RECORD                    = FILLER1
IMPORTING
QID                       =
EXCEPTIONS
   CLIENT_INVALID             = 1
   DESTINATION_INVALID        = 2
   GROUP_INVALID              = 3
   GROUP_IS_LOCKED            = 4
   HOLDDATE_INVALID           = 5
   INTERNAL_ERROR             = 6
   QUEUE_ERROR                = 7
   RUNNING                    = 8
   SYSTEM_LOCK_ERROR          = 9
   USER_INVALID               = 10
   OTHERS                     = 11.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
DO.
perform fill_bdc_tab.
CALL FUNCTION 'BDC_INSERT'
EXPORTING
   TCODE                   = 'XD02'
POST_LOCAL             = NOVBLOCAL
PRINTING               = NOPRINT
TABLES
    DYNPROTAB              = BDCDATA
EXCEPTIONS
   INTERNAL_ERROR          = 1
   NOT_OPEN                = 2
   QUEUE_ERROR             = 3
   TCODE_INVALID           = 4
   PRINTING_INVALID        = 5
   POSTING_INVALID         = 6
   OTHERS                  = 7
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDDO.
CALL FUNCTION 'BDC_CLOSE_GROUP'
EXCEPTIONS
NOT_OPEN          = 1
QUEUE_ERROR       = 2
OTHERS            = 3
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
*include bdcrecx1.
*start-of-selection.
*perform open_group.
*&      Form fill_bdc_tab
      text
--> p1        text
<-- p2        text
FORM fill_bdc_tab.
clear bdcdata.
refresh bdcdata.
perform bdc_dynpro      using 'SAPMF02D' '0101'.
perform bdc_field       using 'BDC_CURSOR'
                              'RF02D-D0110'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'RF02D-KUNNR'
                              itab-kunnr.
perform bdc_field       using 'RF02D-BUKRS'
                              '0001'.
perform bdc_field       using 'RF02D-D0110'
                              'X'.
perform bdc_dynpro      using 'SAPMF02D' '0110'.
perform bdc_field       using 'BDC_CURSOR'
                              'KNA1-PSTLZ'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'KNA1-ANRED'
                              'Company'.
perform bdc_field       using 'KNA1-NAME1'
                              itab-name1.
perform bdc_field       using 'KNA1-PFACH'
                              'GPO'.
perform bdc_field       using 'KNA1-ORT01'
                              '7000091'.
perform bdc_field       using 'KNA1-PSTLZ'
                              itab-pstlz.
perform bdc_field       using 'KNA1-PSTL2'
                              '123456'.
perform bdc_field       using 'KNA1-LAND1'
                              'IN'.
perform bdc_field       using 'KNA1-SPRAS'
                              'EN'.
*perform bdc_transaction using 'XD02'.
*perform close_group.
append bdcdata.
ENDFORM.                    " fill_bdc_tab
       Start new screen                                              *
FORM BDC_DYNPRO USING PROGRAM DYNPRO.
CLEAR BDCDATA.
BDCDATA-PROGRAM = PROGRAM.
BDCDATA-DYNPRO   = DYNPRO.
BDCDATA-DYNBEGIN = 'X'.
APPEND BDCDATA.
ENDFORM.
       Insert field                                                  *
FORM BDC_FIELD USING FNAM FVAL.
IF FVAL <> NODATA.
    CLEAR BDCDATA.
    BDCDATA-FNAM = FNAM.
    BDCDATA-FVAL = FVAL.
    APPEND BDCDATA.
ENDIF.
ENDFORM.
Reward if useful
Regards
ANUPAM

Authorization issue for TR VD01 & VD02

Hi all,
In customer master creation for TR VD01 and VD02 basically we have 3 VIEWS( General data, company code and sales area data). My main requirement is we have 3 sets of users. for one set of users we should give authorization only for creating and changing general view., and other set of users to create only company code data and changing this view. Ie based on views i need to give authorization to the end users. Is it possiable to do this through abap( through user exit) or else this requirement can be done by basis.
Regards,
Smitha.

Hi Suvendu,
Many thanks for your replay,
here for this scenario i am not able to identify which view currently the user is changing(techinically)
Ie in userexit i am not able to identify which view he is currently changing.
How can i distinguish bwtween this 3 views.
Regards,
Smitha

Customer master XD01 or VD01

Hi all,
I have 3 questions
1) What happens if a customer master is created using T-code VD01 and not XD01.
2) Is there any impact this will have.
3) Is it always compulsary to create customer master with XD01.
Thanks
Vikrant

hi,
See there are three in Cust master
general data, comp code data & sales area data
If u use tcode:vd01 only general data &sales area data u will be fill
If u use xd01 u can fill all three data
normally comp code data is filled by FICO end users
rewards if helpful
regards,
Arun prasad

VD01...VL01 screen shots

Hello All,
I will thankfull if some one sends me the screen shots of creation of customer master,
creation material master, creation sales order, cration of delivery and creation of billing
to my mail id [email protected]
I guess there are people who will be in need of these.
VD01 - Create customer master;
MM01 - Create material master;
VA01 - Create sales order;
VL01 - Create delivery;
- create billing; ( is this possible).
Thanks a Ton!
SDN FAN

Also, there are utilities like OnyX that will change the screenshot settings.
But this AppleScript is my favorite.
Screenshot Settings 1.1 <http://scriptbuilders.net/files/screenshotsettings1.1.html>
About:
This application is a GUI method for changing the screenshot (screen capture) settings in Mac OS X v10.4 (Tiger).
Note that you can also drag-n-drop a folder onto this application to change the default location.
Tom

Create Customer Ship to Party (VD01)

Hi!
I'm getting the following message while creating a customer using VD01 in Ship to Party account group in the sales area data--billing document tab- "In table T685A, the entry VJTX4 is missing"

In which field are you trying to give entry, when you get this error message?
Check in V/06 have you created this condition type (VJTX4).
Copy MWST and create your tax condition type, and then go to VD01 and create CMR, maybe you shall not get the error message.

Add VD01 link with button in IW51 Tcode

Hi,
I have a requirement in which I need to add a create button in the Tcode IW51 near Sold To party. this button should allow to create a new Sold to party ( VD01 ) ie. I need a button similar to the one in VA01 to create new Customer. Can you suggest the best possible way for the same.
Thanks and Regards,
Suzie
Edited by: Suzie on Apr 8, 2011 1:58 PM

Hi,
I have a requirement in which I need to add a create button in the Tcode IW51 near Sold To party. this button should allow to create a new Sold to party ( VD01 ) ie. I need a button similar to the one in VA01 to create new Customer. Can you suggest the best possible way for the same.
Thanks and Regards,
Suzie
Edited by: Suzie on Apr 8, 2011 1:58 PM

Customr Master creation VD01 & VD02

Hi All,
Currently we have two set of users in our company let us say A & B.
For user A they should have access only to create only General View and he should not have access to create or change Company code view and sales view for Tr VD01 & VD02.
For Users B they should have access only to create Company code data View and Sales view( only create and change) and he should not have access to change General view for Tr VD01 & VD02.
Is is possiable to control this through User exit or Through the basis people.
KIndly suggest ....
Smitha saran

In SD we have Requirement Routines........This could be possible via that.........Explore the same....

Plz send me the differnce between XD01,VD01&FD01

Hi Friends,
Pls send me reply immediatly,
pls telle me what is the difference between XD01, VD01,FD01
Thanking you,
With regards
Lux.

hi,
XD01 - is used to create a customer centrally ie he is available for comp code as well sales area.
FD01 - is basically used by FI to add company code specific data as sales data cannot be accessed thru this.
VD01 - opposite to the FI, the SD people can add sales area data and cannot access company code data.
The idea of using these t.codes is to provide SD and FI with required access only to the customer master.
Thanks
sadhu kishore

Regading LSMW for VD01 transaction

HI,
This is KSR Saireddy. i am getting the problem in LSMW at the the STEP Create Batch Input Session.i am executing this step,now i am getting the file name as ZIMS_91_ZIMS_91_MIGRT_CUSTOMER.lsmw.conv after excuting it is giving the message that Transaction VD01 not supported can any body please give me answer why VD01 is not supported .

Hi Selva,
LSMW is a detailed 15 Step process to transfer Data from Flat file to SAP System.It is fairly simple provided you have some hand holding for the first time with some ABAP team member.
Please go through the details as mentioned in the [thread|http://sapabap.iespana.es/manuales/pdf/lsmw.pdf].We can discuss it in detail once you are through.
Broadly speaking our purpose in LSMW is to do :
RECORDING PROGRAM:A screen by screen recording of a transaction that we intend to use ( for eg.QP01). These screen by screen records are stored and served as a reference later on.
SAMPLE TXT FILE: This recording gives us a txt file with fields that nees to be replaced with upload file in the same format
UPLOAD FILE: Add all information in the file that you need to upload in SAP in separate rows
EXECUTE BDC:The recording program executes screen by screen in same sequence and uploads the data as in the UPLOAD File.
This description is very simplistic view of LSMW based on my exposure. I am sure that there are many more features than just this (like Filtering, Conversion etc.)
Open up a new thread. We can discuss this in further detail if required.
Thanks,
RAVI.

Screen Exit for VD01 / VD02 / VD03

Hi, I would like to add a custom field to VD01 / VD02 / VD03 - Control Data Tab - Tax Information subscreen. May I know is there any screen exit that I can use to add the custom field? If yes, can you please let me know? Else, what is the other way that I can use to achieve this? Thanks.
Thanks, Nick. G

Pls check this out -
Transaction Code - VD01                     Create Customer (Sales)
Exit Name           Description
SAPMF02D            User exits: Customer master data

User exit in vd01.

Dear all,
in vd01 i am using the userexit sapmf02d.i had activated the userexit and i had kept the break point.even though the control is not passing when i am executing the vd01 tcode.can u pls... help me in this to get the control over there.
-Regards,
HSREDDY

Hi,
can check whether break point is there in any condition . IF condition fails break point will not trigger so check in debugging any condition
Mahendra

Regarding User Exit for VD01

Hi All,
I need to do some special validations based on the partner funstion which is entered during the customer creation through the transaction VD01.
May i know which user exit can be used for the above or any badi can be used
Thanks.

Hi,
User sxit for VD01 SAPMF02D User exits: Customer master data
Regards,
Prashant

FS,TS VD01

Similar Messages

Maybe you are looking for