The purpose of this document is to describe the steps to be done when the password restrictions are preventing STMS from functioning. This document describes the notes to be applied and the execution of report TMS_UPDATE_PWD_OF_TMSADM.

Before proceeding further with TMSADM please ensure that all related notes at the end of this document have been reviewed and/or applied to your system(s) if relevant.

Changing the TMSADM password

The password restrictions are preventing STMS from functioning. Some password restrictions that affect the TMS user TMSADM:

You can also run in SE38 reports RSPFPAR and RSPARAM to get information about the parameters.

Also check parameter login/password_downwards_compatibility, make sure it is set to '1' in all systems. if it is set to '5', it means "compatible to old release" and this forbids lowercase characters.

You will find further information in Profile Parameters for Logon and Password (Login Parameters).

Make sure the RFC's are not manipulated in all systems as detailed by article 1730407 - Internal error in TMS communication 5.

The trusted services are already activated:

You will find further information in Activating TMS Trusted Services.

The user TMSADM was already reset and the RFC’s were generated in STMS:

According to SAP note 1568362 - TMSADM password change, there are two ways of solving this problem. One is to execute some manual steps (as of release 7.3, table TMSCROUTE is not involved in the TMSADM change password configuration.) and the other one is if there is a large landscape, there are some notes to be applied and you should run a report. In this example, we will go with the second option:

1. Apply the following SAP notes in each Domain Controller and in all the other systems of the landscape:
   
   1414256 - Changing TMSADM password is too complex; (for releases <= 640 manual steps in SAP note 761637 must still be applied);
   1515926 - Update #1 to Security Note 1414256;
   1691028 - Fix for TMS_UPDATE_PWD_OF_TMSADM;
   1679157 - Improvement of log for TMS_UPDATE_PWD_OF_TMSADM;
   1801805 - Addition of new destinations in TMS_UPDATE_PWD_OF_TMSADM;
   2201759 - Automatic unlock of TMSADM for password update;
   1968772 - Changing TMSADM Password Changes Host Name in RFCDES;
   1730407 - Internal error in TMS communication 5.
   2222357 - SUSR_RFC_USER_INTERFACE: Dump when you lock/unlock.
   

2. Make sure the user TMSADM is not locked in all the systems of the landscape:

3. Run report TMS_UPDATE_PWD_OF_TMSADM which must be run in the DC (domain controller) client 000.

TMS_UPDATE_PWD_OF_TMSADM has three different options:

1.    Own Password as in System Settings
With this option the customer will select his own created password for TMSADM user. When choosing this option, the following fields are available:
- Password
- Confirm Password
It must be used by the customer to enter the password they want for TMSADM user.

2.    New Standard Password (see SAP Note 761637)
With this option the program will automatically set "New Default Password" for TMSADM;

3.    Old Standard Password
Finally, this option will set the "Old Default Password" for TMSADM user.

The "Old Default Password" is the password that SAP defined for TMSADM user long time ago and it has been used for years by our customers. That password only contains letters. But if a customer sets stringent password rules in a system (for example the password must contain at least one digit, or special characters), user TMSADM is affected by those restrictions. Therefore, SAP has created a "New Default Password" that complies with the general password restrictions that are set in a system. This new password contains uppercase and lowercase letters, digits and special characters.

As of SAP Note  2227412 (or SAP_BASIS SAPKB74014 / SAPK-75002INSAPBASIS).

For security reasons, the TMSADM default password is no longer allowed to be provided. For this reason, the options for this have been removed.

As such when you run Report TMS_UPDATE_PWD_OF_TMSADM you will only get the option to define your own TMSADM password. The same is true when joining a system to the domain or creating a domain link.

The results of its execution:

3. Should domain links exist then use SAP note 1515926. The note should be applied to all systems of the connected domains. Once the note is applied start the report that is described in Note 1414256 on all of the domain controllers of the connected domains. That means executing TMS_UPDATE_PWD_OF_TMSADM in client 000 on all domain controllers.

When domain links are involved TMS_UPDATE_PWD_OF_TMSADM is more complex.

Let's illustrate with an example:

• DOMAIN_A has 3 systems DEV1, QAS1, and PRD1.
• DOMAIN_B has 3 systems DEV2, QAS2, and PRD2.

In DEV1, QAS1 and PRD1 the following TMSADM RFC's exis

1. TMSADM@DEV1.DOMAIN_A
2. TMSADM@QAS1.DOMAIN_A
3. TMSADM@PRD1.DOMAIN_A

In DEV2, QAS2 and PRD2 the following TMSADM RFC's exist.

1. TMSADM@DEV2.DOMAIN_B
2. TMSADM@QAS2.DOMAIN_B
3. TMSADM@PRD2.DOMAIN_B

You link DOMAIN_A with DOMAIN_B.

The following RFCs are added to systems DEV1, QAS1 and PRD1.

1. TMSADM@DEV2.DOMAIN_B
2. TMSADM@QAS2.DOMAIN_B
3. TMSADM@PRD2.DOMAIN_B

The following RFC's are added to systems DEV2, QAS2 and PRD2.

1. TMSADM@DEV1.DOMAIN_A
2. TMSADM@QAS1.DOMAIN_A
3. TMSADM@PRD1.DOMAIN_A

This allows systems in DOMAIN_A to communicate with systems in DOMAIN_B.

As a result when you update the password for user TMSADM in DOMAIN_A (by running TMS_UPDATE_PWD_OF_TMSADM) it will also update
RFCs TMSADM@*.DOMAIN_A in DOMAIN_B (when note 1515926 is implemented to all systems in both domains).

The same happens when you update the user password for TMSADM in DOMAIN_B (by running TMS_UPDATE_PWD_OF_TMSADM). The report will update RFCs TMSADM@*.DOMAIN_B in DOMAIN_A.

As a result communication between the two domains will remain. If note 1515926 were not applied to all systems of both domains and you ran the report TMS_UPDATE_PWD_OF_TMSADM from one or both domain controllers then communication between DOMAIN_A and DOMAIN_B is no longer possible . This is the result of the user TMSADM locking due to too many failed logon attempts with the wrong TMSADM password.

It is important to check (via RZ11) parameter login/password_downwards_compatibility.

As of Basis release (SAP_BASIS) 7.0, the system supports logon with passwords that can consist of up to 40 characters (previously: 8), and for which the system differentiates between upper- and lower-case (previously: system automatically converted to upper-case). All Unicode characters are also supported.

Unfortunately, this change is not backward compatible. The passwords are stored as backward incompatible hash values. If this system is operated with other systems, which only support
backward compatible password hash values, the system must react appropriately.

The values of this profile parameter define the desired behavior (Default value = 1):

0 :  No backward compatibility; system generates only new
(backward incompatible) password hash values.

1 :  System also generates backward compatible password hash
values internally, but does not evaluate these for logons
(to this system) using a password; this setting is required
if this system is the central system of a Central User
Administration and systems that only support backward
compatible password hash values are also connected to the
system group.

2:  The system also generates backward compatible password hash
values internally and evaluates these if a logon using a
backward incompatible password failed, to check whether logo
with the backward compatible password (truncated after eight
characters and converted to upper-case) would have been
accepted. This is logged in the system log; the logon
fails.  (Identification of backward incompatibility problems).

3 :  As with 2; however, the logon is regarded as successful.
(Avoidance of backward incompatibility problems).

4 :  As with 3, but no system log entry is written.

5 :  System only issues backward compatible password hash values.

login/password_downwards_compatibility = 5 will not work with TMSADM using "new standard" password as this means that only downward compatible passwords are allowed, which are in uppercase and max. 8 characters long.

FINALLY :

There is now the addition of new destinations in TMS_UPDATE_PWD_OF_TMSADM because in large systems using the above report is a complex matter.

The TMSADM update report requires an RFC connection for each system in the landscape and if you have a very large landscape it means logging onto alot of systems. Previously, there was no option to use trusted RFC for this. As a result note # 1801805 was created. Please implement the correction instructions in the domain controller (remember if the domain controller changes, the note must be implemented there too) and follow the manual instructions in the note.

Related Notes

1568362 - TMSADM password change
1414256 - Changing TMSADM password is too complex
1515926 - Update #1 to Security Note 1414256
1691028 - Fix for TMS_UPDATE_PWD_OF_TMSADM
1679157 - Improvement of log for TMS_UPDATE_PWD_OF_TMSADM
761637 - Logon restrictions prevent TMSADM logon
1835912 - TMSADM password change across domains with component CTSPLUG;
1730407 - Internal error in TMS communication 5.
1412609 - DUPREC when configuring the transport domain
1801805 - Addition of new destinations in TMS_UPDATE_PWD_OF_TMSADM;
1968772 - Changing TMSADM Password Changes Host Name in RFCDES;
1975845 - RFC_MODIFY_R3_DESTINATION unable to inactivate SNC for destination;

2090808 - Deactivation of TMS SNC

2222357 - SUSR_RFC_USER_INTERFACE: Dump when you lock/unlock.

I have window with two data windows (master and detail)

when i was on master datawindow and press tab ,       

focus changed between column in master until last column (according to tab order) then it focus on first column in detail datawimdow

when it reached to last column in detail datawindow then it scroll to next row of datawindow even that row doesn't belong to master datawindow

how to prevent to scroll to next row if i was at last column in data window?

Hi Experts,

I have created on dash board using OOABAP concetps, dashboard which is use to create and post incoming invoice. Now i want to display all type of messages in popup as the end result of processing the record..

i.e pop should have all types of messages which occured during the processing of the record.

i read some post where i found FM like   : 'MESSAGES_INITIALIZE'  'MESSAGE_STORE' 'MESSAGES_SHOW'.

Kindly tell me functionality of these FM's as your  feedback.

thank you!!

Hi,

I have downloaded the SAP ASE Free Developer Edition 16.0.

I am writing a Windows Forms .NET 4.0 application where I am using the Sybase.AdoNet4.AseClient.dll assembly.

What I try to do is to use the Sybase.Data.AseClient.ConnectionStringEditor class, but I get the following exception:

"MissingManifestResourceException:

"Could not find any resources appropriate for the specified culture or the neutral culture.  Make sure "Sybase.Data.AseClient.ConnectionStringForm.resources" was correctly embedded or linked into assembly "Sybase.AdoNet4.AseClient" at compile time, or that all the satellite assemblies required are loadable and fully signed.""

What should I do to avoid this exception?

Thank you,

Alex

Hello Moderator ,

please publish my last query, I understand now what mistake I have done

Thanks

SL

Hi everyone,

My app crashes when I press "Finish" on the screen set associated to an Add Transaction of an object that is child of Main Object. Any idea why?

Hi ,

We are planning to move reporting ASE server to IQ for better performance .

Question : Can we create proxy table in Sybase ASE  for  IQ table .

What we are trying to achieve :

1) Migrate All  tables /data   to IQ Servers

2) Keep business logic in sybase (Store Proc etc)

3) Create proxy table in sybase which will point to IQ tables

4) Execute proc in Sybase which will extract the data internally from IQ .

So it will not required to rewrite business logic in IQ as we will be using ASE proc which is already there in ASE . No change in Application .

Appreciate your response .

Regards

Ajay Pandey

Hi all,

We are on PI 7.4 single stack.

The issue we are facing is for one of the interfaces to send PO data to vendors HTTP URL..

Interface is FILE to HTTP.

In the message monitor,we see the below error:

Can anyone provide any pointers how to fix this issue?

Hi Experts,

I have to create a new sandbox system using online backup from the production system. I can't take export or offline backup as outage for the production systems is not possible. Can you please give me the detailed document for a system copy (in a new system) in Linux and Oracle?

Also, in this case, the infrastructure team would need to only copy over the /oracle/<sid>/sapdata* , /oracle/<sid>/origlog* and /oracle/<sid>/mirrlog* files?

Thanks for your help.

Regards,

Neha

Hello

we use BIPST 2.0.4 with SAP Host Agent 7.21 and BIP 4.1 SP6 Patch 2.

When running the E2E wizard no logs were collected, but the wizard shows a success message for both application server and web application server.

We had this issue with every BIPST 2.0.x version, but i did not have the time to find the root cause.

Every option for "Create report" works.

The already know issue mentioned in the Release Notes does not apply to us.

Log entries from SAP Host Agent when executing the E2E trace are the following.

[Thr 15496] Thu Jun 30 11:17:03 2016

[Thr 15496] HTTPHandlerManager : HTTP Handler found for /operations-file/9C8E992821DC1ED68FD4685BA0D558C8/0

[Thr 15496] ***LOG Q0I=> NiIWrite: P=XXXXXX:64087; L=XXXXXX:1128: send (10058: WSAESHUTDOWN: Can't send after socket shutdown) [nixxi.cpp 4599]

[Thr 15496] *** ERROR => NiIWrite: SiSend failed for hdl 13/sock 1032

    (SI_ECONN_BROKEN/10058; I4; ST; P=XXXXXX:64087; L=XXXXXX:1128) [nixxi.cpp    4599]

[Thr 3384] HTTPHandlerManager : HTTP Handler found for /operations-file/9C8E992821DC1ED68FD4685BA0D558C8/0

[Thr 3384] Thu Jun 30 11:17:16 2016

[Thr 3384] Operation 9C8E992821DC1ED68FD4685BA0D558C8 finished! Remove from OperationManager

[Thr 1832] Thu Jun 30 11:17:27 2016

[Thr 1832] HTTPHandlerManager : HTTP Handler found for /operations-file/9C8E992821DC1ED68FD46DF08720D8C8/0

[Thr 1832] ***LOG Q0I=> NiIWrite: P=XXXXXXX:64092; L=XXXXXXXX:1128: send (10058: WSAESHUTDOWN: Can't send after socket shutdown) [nixxi.cpp 4599]

[Thr 1832] *** ERROR => NiIWrite: SiSend failed for hdl 19/sock 1148

    (SI_ECONN_BROKEN/10058; I4; ST; P=XXXXXX:64092; L=XXXXXXXX:1128) [nixxi.cpp    4599]

[Thr 14296] HTTPHandlerManager : HTTP Handler found for /operations-file/9C8E992821DC1ED68FD46DF08720D8C8/0

Let me know if you need further information

Thanks & BR,

Michael

Hello everyone,

I am experiencing an issue in MR11. There is a value difference between MR11 and FAGLL03 report.

PO details : PO price is 1 UYU per EA.

First GR was posted with Qty 204,596.250 EA and value 204,596.250 UYU.

Second GR was posted with Qty 245,403.750 EA and value 245,403.750 UYU.

First Invoice was posted with Qty 204,723.810 EA and value 204,723.810 UYU. (Qty and value was changed in this invoice).

Second Invoice was posted with Qty 245,403.750 EA and value 245,403.750 UYU.

In MR11, difference value is 3.97 USD and in FAGLL03 difference value is 3.99 USD.

Following is the MR11 report screenshot :

Following is the FAGLL03 report screenshot :

Following is my analysis :

1. Exchange rate maintained in OB08,

2. Exchange rate in invoice document is '0.03130'.

Invoice document was initially blocked due to qty variance. This document was posted on '24.02.2016' and later released from 'MRBR' on '26.02.2016'.

3. Exchange rate in invoice document is '0.03130' and exchange rate in OB08 on '26.02.2016' is '0.03120'.

4. Report 'FAGLL03' calculation,

Difference amount = 127.560 UYU * 0.03130 (Exchange rate in invoice document)

                            = 3.99 USD

5. Report 'MR11' calculation,

Difference amount = 127.560 UYU * 0.03120 (Exchange rate in OB08 on 26.02.2016)

                            = 3.97 USD

6. System might have considered exchange rate '0.03120' for 'MR11' calculation because the invoice was changed (Released from MRBR) on 26.02.2016.

I am not sure whether my analysis is correct or not.

Does anyone experienced similar issue ? How can we clear the difference between MR11 and FAGLL03 ? Is this is a system bug ?

Appreciate your help.

Hi Team,

We have just migrated from BW 7.3 to BW 7.5 on HANA.

Need you guidance What should we do not to avail the performance benefits . Post migration now the system is up & running but I need to propose what should be the next . Like instead of Multiprovider & Infoset, use Composite Provider, but then what should be then pros & cons, where to use & where not to. Also like start using ADSO , but then again In what scenario, should we go ahead replacing the existing DSO & Cubes with ADSO, In what scenario not to use ADSO etc. Also in terms f reporting what should we can do reduce the runtime on SAP HANA.

Anyone based on such project exposure, Please share so that I can generate case study & present a ROI may be down the line within a year.

Thanks,

need some real time scenarios on interactive report with proper technical specification

Dear Peers and Mentors,

I currently confused about the tab account assignment in the header of

as you can see in picture, in the free good, there is a field cost center appear in there.

I want to ask, how to control what field appear in there ? for example i need to have field internal order in there?

I have done some digging, and i found out that between the sales order and free goods, the field is different because of the sales document category in the order type. for sales order they are C, but for free goods it is I.

I read in the forum that sales document category is pre defined by SAP, and cannot be changed. if that is the case, is it also the same with the field that appear in tab account assignment is also pre defined by SAP and cannot be changed to suit our need?

Thank you in advance for your answer.

Dear All,

We're currently doing table splitting preparation of our BW system.

All the R3ta calls finished with RC code 0. However, even with all R3ta calls finished from OS level, the SWPM GUI still displayed with message that it's waiting for R3ta calls to finish. After close to an hour, the SWPM tool ended with error.

Below is an excerpt from the sapinst and sapinst_dev.log.

ERROR 2016-06-30 06:41:00.189 (root/sapinst) [CSiStepExecute.cpp:1107] id=controller.stepExecuted errno=FCO-00011

The step HdbR3ta with step key |TableSplitter|ind|ind|ind|ind|0|0|TableSplitter_Run|ind|ind|ind|ind|tableSplitterRun|0|HdbR3ta was executed with status ERROR .

We checked the R3ta* logs for each table and there's no registered errors. One WHR file for each table was generated containing the splits.

It looks like the whr splitting phase was not reached.

Our BW system is on NW 7.3 SP10. DB is on DB2 9.7 FP8. All the R3* tools are in latest patch.

We're also using latest SWPM tool SP17 Patch Level 2.

I've been checking notes and SCN links but I haven't seen similar case with above specific step.

Thanks a lot for any inputs.

Best Regards,

Jen

Introduction:

The purpose of this document is to explain about developing a Personnel Calculation Rule to calculate late deduction amount (from Basic Pay wage type).

Calculation formula:

Basic pay wage type to be calculated for the late hours and (from month basic to hours rate) and will be deducted from the employee's salary. You can also add other wage component for basis calculation depends on the requirement. I have taken the example to deduct only from Basic Pay component for illustration purpose.

Input :

We can maintain late coming hours to be deducted Infotype 15 with a wage type 7100 (Late deduction hours). The late hours may also be calculated from time evaluation and can be loaded in ZL. But, for simplicity, I have taken the example of entering late hours in IT15 wage type.

In this scenario,

Basic pay (WT 9000) amt = Rs.19,200

Late Hours (WT 7100) num=0.5 hours

PCR:

Calculation:

Employee's Basic salary is Rs.19,200 (which is AMT field of wage type 9000).

Late Hours is 0.5 hours (in wage type 7100's NUM field).

Calculation Steps:

NUM+ 7100              -> loads the value .5 for calculation.

NUM*10000              -> multiply 0.5 x 10,000 = 5,000

RTE=GKSOLL          -> loads the calendar days of the current month in RTE field

                                        30).

RTE*8                       -> multiply 30x 8 = 240 and store it in RTE field

DIVID NRR               -> divide 5,000/240 = 20.83 and store it in RTE field

NUM/10,000             -> divide 5,000/10,000 = 0.5 and store it in NUM field

MULTI ARA              -> multiply 19,200x20.83 = 399936 and store it in AMT field

AMT/10,000              -> divide 399936/10,000=39.9936 and store it in AMT field

ROUND 100              -> round 39.9936 to 40.00

ADDWT 7100            ->  store amt 40.00 to wage type 7100     

FILLF A,N,R              -> restore original AMT, NUM & RTE values back to wage type 9000 (basic pay)

ADDWT 9000            -> store wage type 9000 back to table IT/OT

Verification:

Month Basic pay amt = Rs.19,200

Per day rate     = 19,200 / 30= Rs.640

Per hour rate    = 640/8 = Rs.80

For 0.5 hours rate = 80x0.5 = Rs.40

Placement of this PCR in Payroll Schema:

This PCR can be placed in sub-schema INAP (import further payment/deductions), if the late hours

are entered in IT15.

PCR should be placed after the function P0015.

PCR can be called as:

PIT ZLTD

eh instalado sap 9.2 y configurado el browser pero a la hora de ingresar a sap no carga contenido solo se queda en pantalla azul sera que alguien me puede orientar en este caso que me falta de configurar o por que tengo ese problema.

Saludos

Hi,

1)We are using condition type MWVZ  in tax Procedure as non deductible input tax. For this condition type assigned NVV account key

2)create I1 Tax code for Non deductible tax code and assined value to NVV

3) Check OBCN  for NVV tax type 2(input tax) and Posting indicator 3( Distribute to relevant expense/revenue item)

4) Create STO Pricing Procedure ZMM001 but we are not defined NAVS in Pricing Procedure.

We have created the Intercomany STO with tax code value I1,   PO for 1qty  Transfer price 100Rs  ( I1  non deductible tax MWVZ is 17%)

While Goods receipt the accounting entries displayed like

BSX: 100 Dr

WRS: 117 Cr

PRD:  17 Dr

Why system generated separate PRD account in Goods Receipt accounting,It should not generate this line item here,why this separate entry showing here at GR level.

Thanks

sapman

Hi all,

I'm struggling with a calculation within Web Intelligence. My use case is that I want to display what is the volume of customer sales but only for the customer with the lowest average price. Customer is not part of the table (or bar chart) as I want to only display this at Country level. Let me give you an example:

I have two countries and the Lowest Price is calculated using the following formula: =Min([Price] ForEach ([Customer])). The Sales Volume is calulated is a similar way. This result in both the min lowest price and min sales volume.

However I need to display the sales volume for the customer that has the min lowest price. This would result in the following table:

Which formula can I use to display the correct value in the Sales Volume column? The difficulty is the fact that I want to filter the sales volume column on that customer that has the min lowest price.

Would be great if somebody can help me with this one! Looking forward to your solutions!

With kind regards,

Martijn van Foeken

One of our customer wants to check the feasibility to disable all the tabs/restrict the content in the tabs except Performance tab in HANA Administration Console.

If anyone has worked on this scenario or has any suggestions, please reach out to me or Narender(in cc).

Note:

We have tried the below options so far:

·        Assigning a role with the CATALOG READ privilege, which gives view access for all data in the console, except Alerts.

·        Assigning a Role with select privilege to all the views under SYS and SYS_STATISTICS schema

thanks,

Ranjith