SAP Library - Find your answers

Question: With the upgrade version to 4.7 regular transactions, do not work the
same way anymore.

Example transaction VL10H on the Tab ‘General Data’ there is column
named OriginDoc. When you click on one of these fields, it calls the
transaction VA03 (In version 4.6C) but now it is calls VA02 (In Version
4.7).

Why and how can I fix that without giving new roles with transactions
they did not have before and that used to run in the background without
requesting any S_TCODE check?

I have many requests for this kind of problem but for different roles
calling different S_TCODE. If I find a way to fix, one I will know for
all the other roles that call other S_TCODE’s.

Someone told me I could use SE97 to skip S_TCODE check BUT! What if the
transaction really require another transaction to work I do not want to
skip it otherwise we will have another kind of problem? Or I am wrong.

Please help

Nancy

Answer:
Sorry I did not find the one I posted yesterday and I thought I did not saved it.

Sorry for the duplicate of S_TCODE check after upgrade to 4.7

Nancy

Answer:
Dear Nancy,

In higher releases of SAP they are cleaning up their navigation paths. Upgrading, when you business process used a path which has changed (it became stricter to click on), does not mean that the process is any different.

You can call anything what you want. E.g. You can use SE97 to MAINTAIN the check on the CALLED tcode based on which tcode is CALLING it. But if the user can switch their sy-tcode, then the relationship changes. Take a look at table TCDCOUPLES.

SAP also provides other confusing messages though, which might be the case here. SU53 says "no auth tcode" ? But this may be caused by your having "BACK"ed (the ESC or OK problem) or the abap didn´t react sufficiently to the check and met a second auth fail, but gave you a message from either the one, or the other and a SU53 from the last check failed... i.e. the last one before '/nsu53'... not necessarily the one which gave you a "message" or caused your navigation path to change.

The change of the called transaction you mentioned (i.e. from VA03 -> VA02) may also be having an implication based on an application auth object check at tcode start, and not the tcode itself. Check SE93 for VA02.

For this you need to look beyond the tcode and compensate for SAP´s max-confusion-strategy. SU53, PFCG, ST01 and the SoD tools loitering around SAP are fully integrated into this strategy.

Kind regards,
Verne

Answer:
The only thing I found in the table TCDCOUPLES is an entry for
TCODE CALLED
VL10H VA03
VL10 VA02

But I am really in VL10H and I keeps having the message
You are not authorize to use the transaction VA02 !!!

I went in SE97 I created a list of called transactions for VL10H
Do not check VA02
Check Warning VA03
Do I have something else to do after what I did or when I use the role everything will work whitout any other configation.

I really need to know how to configure VL10H to call VA03 instead of VA02. Even with the table TCDCOUPLES or SE97 I am not able to change this setting !!!!

Need help
Nancy

Answer:
You will need to,
1. Call SAP and report the problem, or
2. Search on OSS for a fix
3. Debug the code and see if it is configurable in a table ( probably is not and TDCOUPLES has nothing to do with your want, It must be in the code).

Answer:
The last person who called SAP got 335277 - VL10: VA03 instead of VA02 in display of orders

You will need to work together with your developer and application person for the area.

An afterthought: That is also why, when you have outsourced your development work and application consulting, you will need to get yourself a Miles-and-More card and learn at least one exotic foreign language.

Post Installation Task after successful R/3 46c

Generally you need to :-

1. import profiles (default, instance, start) into SAP R3
1.1 add/modify instance parameters such as
rdisp/max_wp_run, abap/timeout,
zcsa/system_languages, and so on...

2. update the R3trans and tp tools with the last ones available on sapnet

3. configure TMS (systems,layer and routes).
You can do it with virtual systems if you have only one SAP system

4. update SPAM/SAINT

5. check via Tcde db02 (with refresh option) the available space for TS other
than SYSTEM TS.( for the others %used must be less than 90)
5.1 check to see critical objects (table/index)
5.2 extend (via sapdba tools -> option TS administration) all TS which
shown critical objectsfor example:
PSAPPOOLD + 200M
PSAPPOOLI + 100M ...
You can get necessary via Note 195446 (for language import) and Note 118823 (for client copy)
5.3 refresh again in db02 and check the %used space

6. import language other than the default (DE & EN) if necessary

7. Client copy

8. configure printer (SPAD)

9. create user

10. change system user password such as SAP* , DDIC, and so on ...

Error you might encounter at the end of client copy :-

"there is a window "change and transport system not configured" Status is cancelled.

To rectify the errors :-

You need to configure CTS via tcde STMS for your SAP system.

If it's your only sap system, then:
- configure it as domain controller: run Tcde STMS and accept the default proposed domain
controller which is your system
- define one or two virtual system (Menu overview-->system then Menu
SAP system-->create-->virtual system)
- Menu Environment --> transport routes then press F5 and Menu Edit
Transport layer to create a "Z" layer for example "ZDEV"
Create a transport route between your real sap system and the virtual system
by using the two layers: "Z" layer and "SAP" standard layer
- save and distribute the TMS configuration
That is the main action you have to do to setup CTS.

Procedure

If you want to use the "assign then store with bar code" scenario to assign a document to an applicant after initial data entry, proceed as follows.

1. On the SAP R/3 System screen, choose Human resources
® Personnel management ® Recruitment, and then Appl. master data ® Maintain.

This takes you to the Maintain Applicant Master Data screen.

2. Enter the applicant number.
3. Choose Extras
® Assign facsimile.

The Document Type dialog box is displayed.

4. Place the cursor on the document type you require and choose Copy.

The Assign Facsimile dialog box is displayed containing information on the current assignment, such as the document type, infotype, and applicant number.

5. Enter the date of origin, if necessary, and choose Continue.

The Confirm Assignment of Facsimile dialog box is displayed.

6. Confirm the assignment.

The Enter Bar Code dialog box is displayed.

7. Stick a bar code on the original document and use an optical scanner to read it into the system. Choose Continue.

A message informs you that the bar code has been assigned successfully.

8. Forward the original document to the scanning department.

Result

Prerequisites

Procedure

If you want to assign a document to an applicant after initial data entry, proceed as follows.

1. On the SAP R/3 System screen, choose Office
® Inbox.

This takes you to the initial screen of your integrated inbox.

2. Use the appropriate function to choose the list that you require.

The system displays the applicant documents sent to you by the scanning department.

3. Select a document and choose Document
® Execute.

4. Place the cursor on the document type you want to process and choose Process.

The Enter Applicant Number dialog box is displayed.

5. Enter the applicant number and choose Continue.

This accesses the entry screen of the infotype linked to the document type you have chosen, or the Maintain Applicant Master Data screen.

6. Maintain the applicant’s infotype record as required.
7. On the infotype entry screen, choose Environment
® Assign facsimile.

The Assign Facsimile dialog box is displayed containing information on the current assignment, such as the document type and applicant number.

8. Enter the date of origin, if necessary, and choose Continue.

The Confirm Assignment of Facsimile dialog box is displayed.

9. Confirm the assignment.

A message informs you that the facsimile has been processed and stored successfully.

10. Confirm the message.
11. If you have made changes, save the infotype record.

Result

Prerequisite

Procedure

If you want to assign a document to an applicant after initial data entry, proceed as follows.

1. Scan the incoming document into the system.
2. On the SAP R/3 System screen, choose Office
® Business Documents ® Documents ® Move.

The system displays a list of presettings.

3. Place the cursor on the required presetting and choose Edit ® Choose.

A list is displayed of document types defined for this setting.

4. Place the cursor on the appropriate document type and choose Edit ® Choose.

5. Enter the applicant number and choose Continue.

This accesses the entry screen of the infotype linked to the document type you have chosen, or the Maintain Applicant Master Data screen.

6. Maintain the applicant’s infotype record, if necessary.
7. On the infotype entry screen, choose Environment
® Assign facsimile.

The Assign Facsimile dialog box is displayed containing information on the current assignment, such as the document type and applicant number.

8. Enter the date of origin, if necessary, and choose Continue.

The Confirm Assignment of Facsimile dialog box is displayed.

9. Confirm the assignment.

A message informs you that the facsimile has been processed and stored successfully.

10. Confirm the message.
11. If you have made changes, save the infotype record.

Result

Prerequisites

Procedure

Result

Prerequisites

Procedure

1. Choose
1. Applicant master data
® Bulk processing ® Receipt of application to reject an applicant who is not assigned to a vacancy.

The Applicants by Actions screen appears.

2. Applicant master data
® Bulk processing ® Vacancy assignment list to reject an applicant who is assigned to a vacancy.

The Vacancy Assignments screen appears.

2. Enter any relevant selection criteria, and choose Execute.

A second Applicants by Action or Vacancy Assignments screen appears.

3. Select the applicant who is to be rejected, and choose Change overall status.

The Change Overall Status dialog box appears.

4. Enter 4 (for Rejected) in the Overall status field, specify a status reason if necessary, and choose Continue.

The applicant is rejected for the entire company and for the assigned vacancy or vacancies. A Letter of rejection applicant activity is created automatically.

5. To print out the letter of rejection, choose fromt he following options:

• Print out the letter individually. See
Printing a Letter for an Activity.
• Print out the letter as part of bulk processing. See
Printing Letters Using Recurring Tasks.

Result

Prerequisites

In order to put an applicant on hold for the entire company after initial entry of basic data, you must carry out the following two steps:

• The applicant's overall status and, if it exists, the vacancy assignment status of the vacancy or vacancies assigned to him or her must be set to On hold.
• A letter informing the applicant that they have been put on hold may have to be printed.

Procedure

1. Choose
1. Applicant master data
® Bulk processing ® Receipt of application to put on hold an applicant who is not assigned to a vacancy.

The Applicants by Actions screen appears.

2. Applicant master data
® Bulk processing ® Vacancy assignment list to put an applicant on hold who is assigned to a vacancy.

The Vacancy Assignments screen appears.

2. Enter any relevant selection criteria, and choose Execute.

A second Applicants by Action or Vacancy Assignments screen appears.

3. Select the applicant you want to put on hold, and choose Change overall status.

The Change Overall Status dialog box appears.

4. Enter 3 (for On hold) in the Overall status field, specify a status reason if necessary, and choose Continue.

The applicant is put on hold for the entire company, and for the assigned vacancy or vacancies. An ‘On hold’ letter applicant activity is created automatically.

5. To print out the ‘on hold’ letter, choose from the following options:
1. Print out the letter individually. See
Printing a Letter for an Activity.
2. Print out the letter as part of bulk processing. See
Printing Letters Using Recurring Tasks.

Result