Go ahead

  -  Somethings you can't control,just go ahead

栏目:02.SAP Tips      5 views

文章来源:https://archive.sap.com/discussions/thread/131118

进行用户,角色,事务代码,用户文档相关搜索时,最常用T.Code:SUIM

User/Security reports

RSUSR000 Currently Active Users

RSUSR002 Users by Complex Selection Criteria

RSUSR002_ADDRESS Users by address data

RSUSR003 Check the Passwords of Users SAP* and DDIC in All Clients

RSUSR004 Restrict User Values to the Following Simple Profiles and Auth. Ob

RSUSR005 List of Users With Critical Authorizations

RSUSR006 Locked Users and Users with Incorrect Logons

RSUSR007 Display Users with Incomplete Address Data

RSUSR008 Critical Combinations of Authorizations at Transaction Start

RSUSR008_009_NEW List of Users With Critical Authorizations

RSUSR009 List of Users With Critical Authorizations

RSUSR010 Transactions for User, with Profile or Authorization

RSUSR011 Lists of transactions after selection by user, profile or obj.

RSUSR012 Search authorizations, profiles and users with specified object va

RSUSR020 Profiles by Complex Selection Criteria

RSUSR030 Authorizations by Complex Selection Criteria

RSUSR040 Authorization Objects by Complex Selection Criteria

RSUSR050 Comparisons

RSUSR060 Where-used lists

RSUSR060OBJ Where-Used List for Authorization Object in Programs and Transacti

RSUSR061 Enter Authorization Fields

RSUSR070 Roles by Complex Selection Criteria

RSUSR080 Users by License Data

RSUSR100 Change Documents for Users

RSUSR101 Change Documents for Profiles

RSUSR102 Change Documents for Authorizations

RSUSR200 List of Users According to Logon Date and Password Change

RSUSR300 Set External Security Name for All Users

RSUSR301 Fill non-checking transactions with auth.object S TCODE

RSUSR302 Delete authorization check on object S TCODE from table TSTCA

RSUSR304 Reload Table TSTCA From Table TSTCA_C

RSUSR400 Test Environment Authorization Checks (SAP Systems Only)

RSUSR401 Report to give all SAPCPIC users profile S_A.CPIC

RSUSR402 Download user data for CA manager from Secude

RSUSR403 Assign Profile S_A.CPIC to User SAPCPIC in Current Client

RSUSR404 Conversion Program for Authorizations of Basis Development Environ

RSUSR405 Reset all user buffers in all clients (uncritical)

RSUSR406 Automatically Generate Profile SAP_ALL

RSUSR406_OLD Automatically Generate Profile SAP_ALL

RSUSR408 XPRA: Conversion of USOBX-OKFLAG, USOBX-MODIFIED for upgrade tool

RSUSR409 Transfer all translated titles to generated transaction codes

RSUSR421 Clean-up report: TSTC-CINFO if no check in TSTCA

RSUSR500 User Administration: Compare Users in Central System

RSUSR500D Report RSUSR500D

RSUSR998 Call Reporting Tree Info System

RSUSREXT Enter Correct SNC Names in Table View VUSREXTID (from SAP R/3 4.5)

RSUSREXTID Enter Correct SNC Names in Table View VUSREXTID (from SAP R/3 4.5)

RSUSRLOG Log Display for Central User Administration

RSUSRSCUC CUA: Synchronization of the Company Addresses

RSUSRSUIM User Information System

RSUSR_S_USER_SAS Activate Authorization Object S_USER_SAS

RSUSR_S_USER_SAS_01 Complete Authorization Data for S_USER_SAS in Roles

RSUSR_S_USER_SAS_02 Convert Authorization Defaults

RSUSR_SYSINFO_PROFILE Report cross-system information/profile

RSUSR_SYSINFO_ROLE Report cross-system information/role

RSUSR_SYSINFO_ZBV Report cross-system information/CUM

User/Security tables

DEVACCESS Table of development users including dev access key

USR02 Logon data

USR04 User master authorization (one row per user)

UST04 User profiles (multiple rows per user)

USR10 Authorisation profiles (i.e. &_SAP_ALL)

UST10C Composit profiles (i.e. profile has sub profile)

USR11 Text for authorisation profiles

USR12 Authorisation values

USR13 Short text for authorisation

USR40 Tabl for illegal passwords

OBJT Authorisation objetc table

栏目:06.杂烩      20 views

2016总结

工作方面:

2015的计划完全没有实现,并且方向发生了非常大的变化。经过一段时间的实践,切实体会到最好还是做自己喜欢的事情。

开始学一些新东西,进度比想要的慢,但整体上在前进并没有中断。

生活方面:

工作/生活的平衡比2015好了一些,勤锻炼完全没做到。

2017计划

工作方面:

1. 新界面的一整套流程要熟悉,达到可以实施的程度。
2. 开发要坚持学下去,达到可以做项目的程度。
3. 五月前搞定5000词。
4. 争取完成一个新界面项目。

生活方面:

多锻炼,多阅读,多写。

标签: , , ,
阅读全文      尚无回复

栏目:02.SAP Tips      18 views

Transactions:

CV01N Create Document (DIR)

CV02N Change Document (DIR)

CV03N Display Document (DIR)

CV04N Find Document (DIR)

CVI1 Create Recipients List

CVI2 Change Recipients List

CVI3 Display Recipients List

CVI4 Recipients of documents

CVI6 Documents of recipient

CVI7 Start Distribution for Recipient List

CVI8 Start Distribution for Documents

CVI9 Log for Distribution

CSD5 Where Used List, Single Level Document

CC04 Product Structure

SPRO T.Codes:

DC10 Define document type

DC20 Define data carrier

DC30 Define workstation application

OAC0 Maintain Storage System

OD00 Number range for document

标签: ,
阅读全文      尚无回复

栏目:02.SAP Tips      20 views

Add-on的表和标准表都可以改

1. SE37
2. Function Module:SE16N_INTERFACE
3. I_TAB:Table Name I_EDIT:X
4. 点击运行,进入修改界面

栏目:02.SAP Tips      16 views

Reference1:link
Reference2:link

Download:CG3Y
Upload:CG3Z

具体操作参照下边文章:
=====================

Introduction

When you are doing development work or customizing in a SAP system your changes will be written to a transport request. Once the work is finished, the request will be transported to another system (test or production system).
The source and target systems of such a transport route are defined in the SAP system customizing. In case you want to get direct access to a transport file, e.g. to transport modifications to a third system that has not been included in the transport route yet, you need direct access to the file system to copy the transport files manually.

This blog demonstrates a simple way to download released transport requests from an SAP system without accessing the file system directly.

Directions

This blog assumes that you have sufficient authorizations to perform the steps specified below.
Make sure the steps are compliant to your company’s organizational and security guidelines!
You have to release the transport request before you are able to download it to your local machine.

1. Know your transport request
First you have to keep in mind the name of the transport request XXXKYYYYYY you want to store (e.g. A07K123456).

2. Find the transfer directory of the SAP system
Releasing a transport request forces the SAP system to store the request in two files on the server: one header (also known as “co-file”) and one body file (also known as “data-file”). To download these files you have to figure out the system specific settings in which directories the files will be written.
Therefore, run transaction AL11 in which the directory parameters can be accessed.
Search for the “Directory Parameter” DIR_TRANS and note the corresponding “Directory” (e.g. [file://myserver/saptrans/|stage:\\myserver\saptrans]).
The header- and the body file are stored in different directories on the server. The next step will show how to figure out their names.

3. Find name and directory of the request header file
A double click on the entry DIR_TRANS in transaction al11 displays the corresponding content.
Beside other entries you will find two sub-directories called “cofiles” and “data”.
First, double click on “cofiles” to enter this directory. Here you should find the header file of your transport request with the following naming syntax: KYYYYYY.XXX (e.g. K123456.A07). You can use Crtl+F to search for it. If you have found your file note the entire directory name (displayed above the table, e.g. file://myserver/saptrans/cofiles) and the file name (e.g. K123456.A07).

4. Find name and directory of the request body file
Return to the DIR_TRANS directory and open the “data” sub-folder. You should find the body file of your transport request in here with the naming syntax: RYYYYYY.XXX (e.g. R123456.A07). Note directory and file name as well.
If you cannot find your files, either the release of the transport request failed or there are other sub-directories defined in your system!

5. Call function module to transfer the files
Now you are able to download the two files from the application server to your local file system. To download the files you can use the standard function module ARCHIVFILE_SERVER_TO_CLIENT. Use se37 to execute the function module.

The function module requires as importing parameters the full qualified paths a) from the source- and b) from the target system including the filename.

To get the header file, the parameters might be:
[stage:Source] PATH: file://myserver/saptrans/cofiles/K123456.A07
TARGETPATH C:\Temp\K123456.A07

And to get the body file the parameters should something like:
[stage:Source] PATH: file://myserver/saptrans/data/R123456.A07
TARGETPATH: C:\Temp\R123456.A07

The downloaded files can be used to be imported into another SAP system.

Additional Steps

If you have to download transport requests this way very often, the procedure described above is very time-consuming.
So it might be an interesting option to further automate this process.
Below you find the basic idea to create your own program / transaction:.
Prompt for the transport request name and the local directory as input parameters.
Then you can use the statement
CALL ‘C_SAPGPARAM’ ID ‘NAME’ FIELD ‘DIR_TRANS’ ID ‘VALUE’ FIELD lv_dir.
to get the DIR_TRANS directory.
With knowledge about the (static) sub directories as well as the naming syntax of the transport request co- and data-files you can now assemble both server source paths and (in combination with the prompted local directory) the target paths.
Finally call the function module ARCHIVE_SERVER_TO_CLIENT twice (with the assembled source and target paths) to copy the files to the local system.

栏目:11.SD      9 views

1. BS02 – Create status profile
2. Assign Object Types to status profile
3. Create Release status
4. Define Influence and Next action for each status
5. Assign status profile to Document type

Reference: http://sapfunctional.com/SD/ReleaseStrategy/Index.htm

栏目:01.SAP MM      28 views

Source: http://www.cnblogs.com/Steveson/archive/2010/04/27/1722097.html
Reference1: https://archive.sap.com/discussions/message/8378030
Reference2: http://forums.sdn.sap.com/message.jspa?messageID=8742391
The more information, you can refer to: SAP Help

The system carries out the following activities in order to determine the release strategy for a purchase requisition. Filling the communication structure When you process a purchase requisition, the system passes on the data from the document to the communication structure CEBAN. Certain fields of the latter are determined from the requisition data prior to the transfer.

For example, the total value of an item is determined and passed on in this way.

Note If you wish to use fields that are not included in the communication structure CEBAN to determine the release strategy, you must insert the relevant fields in the communication structure CEBANZZ. Via the customer exit M06B0002 (item-wise release) and M06B0005 (overall release), you can then include in the communication structure data that is not included in the structure in the standard system.

Example The responsible cost center manager is to be determined for a cost center in the purchase requisition. This data is read fom the cost center master record, inserted in the field USRC1, and passed on to the communication structure CEBAN. After the data has been passed on to the communication structure, the system initiates an object search:

1. The document type of the purchase requisition determines whether the latter is released in total or item-wise.

2. The system determines the relevant class via the type of release (overall or item-wise). Note Only one class is allowed per type of release. This means that you must assign the same class to all release groups valid for overall release, for example. When defining release procedures for purchase requisitions, you must thus create a maximum of two classes: one for overall release and one for item-wise release.

3. The system assigns the values from the communication structure CEBAN to the characteristics of this class.

4. Via the object search function, the system then identifies a release strategy whose characteristics accord with the values from the communication structure or lie within the specified interval.

The following search results are possible:

1) Just one release strategy is found. The system assigns this release strategy to the purchase requisition.

2) Several release strategies are found. The system assigns the first release strategy found to the requisition.

3) No release strategy is found. The system does not assign a release strategy to the requisition.

The latter can be converted into a follow-on document without having to be released.

(http://forums.sdn.sap.com/message.jspa?messageID=8742391)

– – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –

In standard design system only considers characteristics from CEKKO structure for release strategy consideration. But it will not stop us in selecting the other characteristics. Please go through the IMG help of release strategy, will give good information. I think you have already read the note: The characteristics of the class used must all be linked to the corresponding fields of structure CEBAN or CEKKO (for purchase orders)….” Characteristics which are created for the release strategy with classification MUST access communication structures CEBAN or CEKKO since during the strategy determination, the system cannot access any other tables or structures.

If the characteristics refer to fields which are not contained in structures CEBAN or CEKKO, the corresponding fields can be added to communication structure CEKKOZZ or CEBANZZ, or an append structure can be created for CEKKO or CEBAN in which new fields can be included. If you want to use new defined fields as part of the release strategy clasification, you should use enhancement M06E0004 (User exit “exit_saplebnd_002”).

This user exit allows you to use the user fields in strucure CEKKO to include additional data. Use the user fields of this structure: USRC1, USRC2, USRN1 or USRN2 and control them through user exit “EXIT_SAPLEBND_002. Otherwise new field will not work.

As you very well know SAP has provided the following customer exits which allow us to change the communication structure for determining the release strategy:

* Purchase requisition M06E0002 – for item wise release

* Purchase requisition M06E0005 – for overall release

* External purchasing document M06E0004

(https://forums.sme.sap.com/message.jspa?messageID=8378030)

标签: , ,
阅读全文      尚无回复

SAP SMTP Configure

栏目:02.SAP Tips      16 views

参考:
https://blogs.sap.com/2013/09/17/configuring-sap-smtp-service/

标签:
阅读全文      尚无回复

栏目:02.SAP Tips      26 views

SAP WebDynpro激活
Reference:SAP WebDynpro配置

HTTP 403处理
将WebDynpro程序从DEV传送到QAS之后,Webdynpro程序出现HTTP 403错误。

原因:该程序所对应的Service没有激活。
解决:T.Code:SICF \default_host\bc\webdynpro\sap\* 找到对应的WebDynpro程序,将其激活。

栏目:02.SAP Tips      18 views

在HR模块PPOME维护科目设置的时候,可能会出现下述错误信息。

Controlling area already used for org. unit problem

解决方法:

将Controlling area分配给最上层的组织机构,这样所有下层组织结构就能进行继承。

标签:
阅读全文      尚无回复

Page 1 of 3712345...102030...Last »