Hello Mortiz,
Check the previous parameter is changed again back to its original value or whether it remains with updated one.
Please paste DEV_DISP log
Regards
Anand
Hello Mortiz,
Check the previous parameter is changed again back to its original value or whether it remains with updated one.
Please paste DEV_DISP log
Regards
Anand
Hi Madhusudan,
Did you find any solution for your problem? I am also facing same issue with decision table on analytical view. Please share if you have got solution.
Thanks,
Shriniwas
Hello
Check if this is related to Authorisation issue.
Also this could be an issue due to instantiation of Decoupled infotype buffer and old buffer.
Can your post the code that this triggered during approval.
Regards
sandy
Sjoerd - similar to Mustafa, I get the right results too with Design Studio 1.5 on a BW 7.02 old sandbox.
What BW release are you using?
Raghava sir
while doing goods movement in MB1A or MIGO i was not getting Movement type 321 in client server so i maintained in OMJJ .
Regards
Sudhanshu
Sun,
We know that it is possible in ECC through fixed lot size, but for the extra 700L(SFG) system should automatically propose the plan to pack in SKU's(FG) based on the sales forecast.
If you have a sales forecast, why aren't you including it in your planning demand? System would automatically continue to build your SFGs into FGs until your forecast has been fulfilled.....
Best Regards,
DB49
It is because when you are filling t_cosel it is running the AT SELECTION-SCREEN events, it is not the second AT SELECTION-SCREEN causing the problem.
Put a break-point just after both your at selection screen statements and then you can quite easily see what is happening.
Hi
In the Source system you have to create the archive location and the same path provide in the target system.
Regards
SS
By the way, this movement type (100) is not limitted per depr. areas?
Hi,
test after updating below parameters in the webi block.
Amit
Hi Shikha,
Check question 8 and 12 in below SAP Note for more details.
SAP Note 913858 - XI Alerting: Troubleshooting
Regards,
Praveen.
Guys,
We have one BSP application in Portal. The problem is whenever i click the exit button, i am getting the session time out error. I am not much in to portal and i am not sure which parameter to change since all is going to be in configuration.
Can any one help me in sorting out the problem ?
This is the error i get when i execute the application from portal. But when i do directly from SE80, i do not see any problem
Changing the life time of the status would help ??
Thanks,
Karthik
Hi, everyone!
Might someone take a look at this and spot my mistake?
What this is, is SAP's example preferred agent IVR customized to check a list of queues instead of checking just one or every queue:
# coding=latin-1 from __future__ import with_statement import VER VER.VER(__file__, """ Company: SAP Filename: PreferredAgentCustomizer.py Description: Custom method(s) for finding a preferred agent for the call. Created: 08.04.2014 Modified: - """, '1.0.0.0') from Env import * from ICustomize import * from CEMODBC import ODBCConnection from SBTools import AGENT, QUEUE from Tools import TRIM_SQL, makefilter class PreferredAgentCustomizer(ICustomize): # ======================================================================== def __init__(self, AppConf): # Call the base class constructor ICustomize.__init__(self, AppConf) # ======================================================================== def FindPreferredAgent(self, params): """ Find a preferred agent for current call. <params> is a dictionary containing the parameters passed in from the application, plus a reference to the application's state machine, available with key "SM". Parameters: MonitoringHistoryDSN : string : Monitoring History database connection string ANumber : string : Alternative a-number to be used in search - if not given, SM.CALL["ANumber"] is used by default QueueID : string : Only search previous contacts from this queue (optional) MaxContactAge : int : Maximum age (in seconds) for the previous contact - if not given, a value corresponding 30 days is used by default Returns: Extension number of the preferred agent, or None if the agent was not found. """ try: SM = params['SM'] dsn = params['MonitoringHistoryDSN'] if not SM: raise RuntimeError('Invalid value for mandatory parameter [SM]: [%s]' % SM) number = params.get('ANumber', SM.CALL['ANumber']) queueIDs = params.get('QueueID') queueIDs = queueIDs.split() maxAge = params.get('MaxContactAge', 60 * 60 * 24 * 30) if not dsn: # We need Monitoring History database connection string in order to continue raise RuntimeError('Invalid value for mandatory parameter [MonitoringHistoryDSN]: [%s]' % dsn) # Perform rudimentary caller number validation number = makefilter('0123456789')(None, number) if not (len(number) >= 3 and number != 'CLIR'): WRN('PreferredAgentCustomizer.FindPreferredAgent : Cannot search using caller number [%s]' % number) else: if queueIDs: # Validate the given queue identifier for queue in queueIDs: raise RuntimeError('%s' % queue) exists = QUEUE.FIND(queue, None, None) if not exists: raise RuntimeError('Queue with identifier [%s] not found' % queue) # Replace possible queue extension number with queue GUID # queueID = queue['GUID'] # Try resolving the user GUID of the agent who most recently answered the call from <number> userGUID = self._DoFindAgent(dsn, number, maxAge, queueIDs) if userGUID: # Validate the user GUID against CEM's agent store agent = AGENT.FIND(userGUID, 'USER_GUID', None) if agent: # The agent is still known by CEM: return her extension number result = agent.NUMBER else: # The agent (user) has probably been deleted from the system... WRN('PreferredAgentCustomizer.FindPreferredAgent : User [%s] not found' % userGUID) except Exception, err: EXC('PreferredAgentCustomizer.FindPreferredAgent : %s' % str(err)) return 'ERROR' SAFE('PreferredAgentCustomizer.FindPreferredAgent : OK') return ('OK', result) # ======================================================================== c_SQL = \ TRIM_SQL(""" SELECT TOP 1 [Value1] AS [UserGUID] FROM [TAContactLog] cl WITH(NOLOCK) INNER JOIN [TAContactLogDetail] cld WITH(NOLOCK) ON cld.[ContactLogGUID] = cl.[GUID] WHERE cl.[Source] LIKE ? AND cl.[QueueGUID] <> ? %s AND cld.[Event] = 'ConnectedToOper' AND cld.[TimeStamp] >= DATEADD(ss, ?, GETUTCDATE()) ORDER BY cl.[TimeStamp] DESC""") def _DoFindAgent( self, monitoringHistoryDSN, callerNumber, maxSecondsSinceLastContact, queueIDs, ): """ Perform the agent search in Monitoring History database. Note that direct calls are excluded from the search -- in order to include them, remove the first AND condition from the query and the corresponding parameter value (Env.c_OperDirectName) from the statement parameter list. """ result = None if len(callerNumber) > 8: # Search using last 8 characters callerNumber = '%%%s' % callerNumber[-8:] if maxSecondsSinceLastContact > 0: maxSecondsSinceLastContact = -maxSecondsSinceLastContact # Connect to database connection = ODBCConnection(GUID(), self.m_E, monitoringHistoryDSN) # Prepare the SQL statement and run the query query = self.c_SQL % (" AND cl.[QueueGUID] IN (") for queue in queueIDs: query = self.c_SQL % (("'%s'," % queue if queue else '')) query = query[:-1] query = self.c_SQL % (")") parameters = (callerNumber, Env.c_OperDirectName, maxSecondsSinceLastContact) resultset = connection.execute(query, parameters) if resultset is not None and len(resultset): result = resultset['UserGUID'] return result
I've not yet tested if it works (so there might be logic errors), since every time I activate it I'm greeted with the following error:
12:51:15.577 (03672/RelThr:POLL_ChangeTrack) ERR> [EXC] : ImportCustomizer : Exception : '5F75F7DC-FFA2-4991-B652-909A9CCC0CF7'
12:51:15.577 (03672/RelThr:POLL_ChangeTrack) ERR> <type 'exceptions.KeyError'> : 'PreferredAgentCustomizer_queues'
12:51:15.577 (03672/RelThr:POLL_ChangeTrack) ERR> File: .\ConfMultiAppl.py (3359) Func: ImportCustomizer <None>
This seems to indicate that some dictionary is missing the key that is currently being requested. Which dictionary - I have no idea
I'm also quite stuck since I'm currently having a hard time thinking outside the box.
So, once again, could anyone take a look at this with a different angle and point out what causes the KeyError?
Best wishes,
Jaanus
Hi,
Did you already solve this mate?
Regards,
Loed
Hi Audrey,
Can you attach a screenshot.
Regards,
Shreejith
Dear Didyendu ,
thanks for your fast response , but I still didn't get what is the cause of the issue , how transaction type field that affect consolidation statements related to asset posting journal.
when I check OB41 I found that all the transaction type field status of the posting keys used in the document 70 , 40 ,31 are optional.
In OB14 transaction type field status the reconciliation account of assets 17060 is optional but the expense account and vendor recon. account are suppressed , so shall I change it to optional ?
Hi Arnold,
The second option was not correct solution , misunderstood my bad.
Just check not equal operator working or not in Dimension override.
if its working then
BAS(ALL) AND ID<> I_E.3000
Shrikant
Please refer this image and the error message below:
The error says:
Message no. CM_PIQ_API202
An error occurred during pricing of an item.
The system issues an error code and marks the pricing result as incorrect. The following codes are available:
Investigate the root cause of the error indicated by the error code and solve it.
Thank you.