Ups...
"Have to be done in single line!"
TASK(/CPMB/CLEAR_CUBE,SELECTION,%SELECTION%%HARDCODEDDIM1%%HARDCODEDDIM2%%HARDCODEDDIM3%)
Hope, now it's clear!!!
P.S. Same for:
TASK(/CPMB/CLEAR_COMMENTS_FOR...
Ups...
"Have to be done in single line!"
TASK(/CPMB/CLEAR_CUBE,SELECTION,%SELECTION%%HARDCODEDDIM1%%HARDCODEDDIM2%%HARDCODEDDIM3%)
Hope, now it's clear!!!
P.S. Same for:
TASK(/CPMB/CLEAR_COMMENTS_FOR...
Hi Experts,
We have to upgrade CRM 5.0 to CRM 7.0 .
For this we require to know the product master data maintenance in CRM 7.0
We are presently using the PME tool for the product master data maintenance.
Request to let me know the impact and the prerquisites for the migration from 5.0 to 7.0.
Thanks
Rishika
It does not work. Still creates the pdf in the ftp with one 1kb.
Any other ideas?
Thanks Aaron.
Hi Victor,
When I click on the SQL Assistant button to create a new object, the SQl Expression Editor window which generally opens to append to the database column does not open up.
Hi KC;
The only way to know for sure is to try it. IM 11.5.1 was the 1st version to be certified for W7 - but, others have had luck with older IM versions (depending on the features used).
Good luck!
Regards ... Chris
Thanks guys,
I already have the Funtion library which is assigned to the mapping, I can see it from Enterprise service browser of NWDS but from the the BPMN process development I dont see these function libraries. Is there something that I need to do to make this visible in process development view of BPMN?
Regards
Kalyan.
Hi,
The note tells about AlwaysOn which runs on WFCS framework but, it is not the usual SQL Server installed as a Failover Cluster. Please save some time to read the blog series about AlwaysOn: http://blogs.msdn.com/b/saponsqlserver/archive/tags/alwayson/
Log Shipping would be a solution for example in case you were running SQL Server 2008 R2 or early versions. With AlwaysOn you can create an Availability Group, set a listener and set your primary and secondary replicas.
The secondary replicas can be either synchronous (required for automatic failover) and the asynchronous (which is similar to the database mirroring).
You can perform automatic failover between the Synchronous replicas (SQL Server 2012-2014 allows 2 synchronous replicas to failover automatically between then, SQL Server 2016 will increase to 3), and the asynchronous secondary replicas can only be failed over manually, as they're not always synchronized.
Each replica (node) has its own storage and doesn't share with the others.
You can use the other replicas to perform jobs like log Backups and full backup (copy only), as well run some jobs that doesn't alter data.
It requires some time to study, plan and deploy, but you can be like invincible with AlwaysOn.
But in case you want to stick with Log shipping and other methods of DR with SQL Server, you can refer to notes 965908 and 2021980.
Best Regards,
Luis Darui
Thanks Edward, this is my first post ever here; thanks for your observation!
Check the table TADIR.
PGMID : R3TR
OBJECT : TABL
OBJ NAME : Table name.
Check the field CREATED ON 07/29/2015.
The other option would be to use DD02L and sort the result by fields "AS4DATE" and "AS4TIME" and pick the first record.
V.
Hello everyone,
I'm having problems with the following query. I tested on HANA Studio and had no problems but when I try to use it on SAP B1 I get errors:
SELECT
CASE WHEN LENGTH($[OIGE."U_BCS_AREA"]) < 3 THEN (SELECT DISTINCT E."FormatCode"
FROM
"OITM" R
INNER JOIN "OITB" W ON W."ItmsGrpCod" = R."ItmsGrpCod"
INNER JOIN "OACT" E ON W."DecreasAc" = E."AcctCode"
WHERE
R."ItemCode" = $[IGE1."ItemCode"])
ELSE (SELECT Q."U_BCS_Cuenta" CTA
FROM
"@BCS_SALIDA_STOCK" Q
WHERE
Q."Code" = $[OIGE."U_BCS_AREA"]
AND Q."U_BCS_Interno" = 'N')
END
FROM DUMMY;
Error message:
Any suggestion will be helpfull.
Regards
Juan Antonio Jimenez
Good evening Mohan,
Sorry for the late response. SAP has created a new report for this requirement in release: 1505.
Please check it out.
Kind regards,
Emeka
Hi
Sorry just search after posting
There are already 2 notes released by SAP for the problem
2189078 for Lock booking error
2154626 for subnodes disappear issue
In case you have issue only in display of booking Please check 2104647
Thanks
Syed
Hi,
Your coding could look as follows:
DATA:
l_t_wbs_elements TYPE STANDARD TABLE OF bapi_wbs_elements,
l_s_wbs_elements TYPE bapi_wbs_elements.
l_s_wbs_elements-wbs_element = <your wbs element>.
APPEND l_s_wbs_elements TO l_t_wbs_elements.
CALL FUNCTION 'BAPI_BUS2054_GET_STATUS'
* IMPORTING
* RETURN =
TABLES
i_wbs_elements = l_t_wbs_elements
* E_SYSTEM_STATUS =
* E_USER_STATUS =
* E_RESULT =
.
Best regards,
Sander
Good evening Priya,
Sorry for the late response. Thanks for the update. My former colleagues will get back to you on it.
Kind regards,
Emeka Ikwukeme
A few years back we cheated and used something called dddll.dll to achieve this functionality.
Thank you for responding Ludek.
At this juncture I am not dealing with a load balancer (I am using my development machine and storing the session state on a server within my domain for testing). So the use of "Sticky Sessions" does not really apply to my dev machine (I don't think).
Can you advise if I am wrong about that please?
I have upgraded to 14 and the problem is the same.
Is there anything else I might be missing?
As always, I appreciate the help!
Nope, but if you have detailed reporting you can create a report.
Hi,
We have a requirement to create a payment term where invoices pay on the 1st & 15th.
I have started working on this and I am using the day limit functionality. The term is working correctly, however the business unit wanting this term, only wants to pay on the 1st & 15th. In an invoices misses the 1st, currently the payment is being made on the next payment run. We pay daily so the items paid on the 2nd.
The business does not want this, if the payment misses the 1st, they do not want the payment made for those invoices until the 15th.
I do not know how to do this with configuration. Does anyone know how to do this with configuration?
Eagerly awaiting your responses and ideas!!
Thanks
Alicia
And the plot thickens...
I see the exact same effect when the Reference utilizes an AK (unique constraint) on the Parent Table, rather than the PK. In such cases, it replaces the Join Columns on the Child Table with new "fake" instances (which are copies of the AK columns), while duplicating their counterparts on the Parent Table.
In all both cases, I am able to correct the error manually after import, but it seems that there should be some way of properly defining the dependencies on the spreadsheet to avoid the problem.
Anyone has a thought?
Regards,
- j.
Thanks for your detailed reply.
Re: Yes you should always quiesce the replication path before making changes to subscriptions.
Good to know, but I couldn't find this anywhere in the documentation when adding a new table to an existing publication/subscription. If this is a requirement, it really needs to be written down somewhere.
Re: You would not have to stop the rep agent when marking the table (if the "replication path" is quiesced)
So "quiescing the replication path" here includes a quiescing primary (active) database. Ok.
Again, the sp_setreptable man pages say nothing about stopping the rep_agent. The doc's do say to make sure the repdef exists first.
A repserver 15.5 tech overview doc I have (dated 5/4/2010) talks about being able do alter repdef on the fly and the repserver will be able to keep track of which data is using which repdef.
Re: When changes are made to subscriptions it will place a marker in the primary database
Really? A subscription change in a downstream repserver will execute an rs_marker command in primary (er, "active") ASE server that's not even connected to the downstream repserver? Are you talking about alter repdef?
Re: why you are not using a database repdef and database subscription for replication.
We've thought about this and it's a possibility someday.
One minor problem, for the rep_maint user that the DSI uses to run the actual insert/delete/update statements (non schema change commands), we alias rep_maint to dbo so we don't have to do lots of grants.
But we have to drop the rep_maint alias to db and add a real rep_maint user when running rs_init (it needs a real rep_maint user).
When we drop the rep_maint alias for a primary (active) db, it causes errors for db subscriptions (aka MSA replication).
So I guess we have to figure out how to setup a rep_maint user in a db to have dbo privileges in that db without aliasing rep_maint to dbo.
Ben