Restrict the posting period opening and closing for some users

Dear SAP gurus,
I want to restrict some users to open the posting period and for some users close posting periods. I knew that these can be done through authorization group. Pls explain how to create authorization groups and how to use those? Anybody can help me out?
Regards,
Venkata Reddy

Dear Venkatareddy,
There are two sets of period in OB52. The first set of "From" and "To" is for the authorised group and second set is for the non authorised group. In the "Authorisation Group" (last column) give some 4 charecters name. Say "FICO".
Now ask the basis to attach the object "FICO" for the users who are authorised say user1, user 2 and user3.
Now in the first set of period you can maintain say 1 2008 to 16 2008 and in the second set 1 2008 to 1 2008.
So except user1,2 and 3, all the others can post only in 1 2008. Whereas users 1,2 and3 can post in all the periods of 2008.
Assign points if useful
regards
Venkatesh

Similar Messages

I just upgraded to OSX version 10.8.3 and since then all animations are defective. The dock is jerky! The effects of opening and closing windows ranging in shots! What should I do?

I just upgraded to OSX version 10.8.3 and since then all animations are defective.
The dock is jerky!
The effects of opening and closing windows ranging in shots!
What should I do?

You can check the status of your drive's indexing by clicking the Spotlight menu to see if there is a progress bar at the bottom of it, and can also open Activity Monitor and click the "%CPU" column to sort by CPU usage, to see if the processes "mds" or "mdworker" are currently active and using your CPU.
If so, then wait for them to finish. However, if not then try rebooting and then hold the Shift key immediately after you hear the boot chimes. This will load the system into Safe Mode, which should run some checks and maintenance routines on the system. Then reboot normally to see if the problem persists.
How much RAM do you have installed on your system? You can see this by choosing About This Mac from the Apple menu.

HT4528 the camera on my iPhone 4s color is all weird and the shutter keeps opening and closing trying to fix its self but cant. I rest my phone and turned it off and back on again.. how do i fix this. I only had the phone maybe six months.

The camera on my iPhon 4s is not working correctly. It is colored all strange and the shutter keeps opening and closing trying to fix the problem but it cant. I have already reset my phone and turned it off and on again. How do I fix this??

If resetting the camera app doesn't work you can try restoring your iPhone's software. The entire process takes about an hour to an hour and a half. Make sure you do a backup. Make sure you do a backup.
Backup:
http://support.apple.com/kb/HT1766
Restore:
http://support.apple.com/kb/HT1414

PPT unable to open in browser for some users

PPT unable to open in sharepoint browser for some users?

Hi,
If the issue only occurs to some users not all, I’d recommend you check client issue and permission issue. For client issue, you could try compatibility view in IE.
If there is more than one WFE servers in your environment, then please ensure SharePoint Shared Services is started on all WFE servers.
Here is a link which provides solution to similar issue, for your reference:
http://support.microsoft.com/kb/2028346/en-us
If it doesn’t work, please provide more specific information about error message to narrow down the issue.
Regards,
Rebecca Tu
TechNet Community Support

Period Opening and Closing

Hi Gurus,
Please explain for Period Closing and Opening we have to do only MMPV or is there any step by step procedure is there.(incl.for all the Modules)
Tks.

hi
MMPV Close Period for Material Master Records
Once the system is in productive operation, you normally run the period closing program once a month at the beginning of a new period. This program sets the new period, making it possible to perform goods movements with reference to the new period.Once the period has been closed, it is no longer possible to make postings to what was the previous period
MMRV Allow Posting To Previous Period
in this the Allow Posting to Previous Period Indicator that allows posting to the previous period (backposting). In this case, the previous period is the preceding month.
MMPI Initialize Period for Material Master Records
For FI you Can Use OB52
for help of OB52 check following
http://www.sap-img.com/zf011.htm
hoep it help
regards
kunal

Period opening and closing with relation to Parked document

We have the process of parking the document and then posting the same through T code: FBV0. Every month we park the document.
Many times it happens that the period is closed without posting the parked documents. Do we have any way where we can check during doing the Transaction code OB52 which will give the message that posting period cannot be changed unless and until the parked document are posted
Prashant P Zinge

Hi,
Your requirment is not available in Standard SAP.
Parked documents can be posted in any month in a FY, some times at the end of FY also.
SAP have a possibility to delete all the parked documents related to previous FY at the begining of new Fiscal Year to start new Parked documents for new FY.
Thanks
Chandra

Period Open and Closing

Hi Gurus,
As today is 1st april and we have fiscal year April to March.
I opened 1 to 16 periods in 2007, so what should i do to open periods for 2008????
What changes should i make in periods of 2007???
Please revert asap.
Thank You

Hi
T code: OB52
in the from Period 1 you give 1 (April)
                Year :2008
           To   Period you give 1 (April)
              Year : 2008
Period 2 you give 12 (March)
                Year :2007
           To   Period you give 16
              Year : 2007
By this April 2008 will be opened and March 2007 including special periods will be opened

Folder created in System form and disabled for some users.

Hi,
I have created a folder in Inventory data form and work well for every users who have professional licence with R/W permission for that form. If a user with CRM licence access the Inventory data form, he see my folder disabled.
If I put these users in R/W, all is OK : everyone can access my folder. But, I won't let it like this... If I won't grant R/W access to everyone and get back to R only, I will loose that property.
Q: How to make that folder activated for all users what ever the licence he has ?
Thank you.
Edited by: Kevin Bedard on Oct 29, 2008 4:37 PM

HI,
The crm user has only R rigths in the license. I think the form is only in view mode (check the form mode from debug)
Even the form is in OK mode, not view mode:
Try:
1. get the form_activate event
2. Enable the folder even it is disabled.
Regards,
J.

AnyConnect pre Windows login connects and disconnects for some users

Hi,
I have Cisco VPN AnyConnect (version 3.1.0310) clients with a connectivity issue which manifests as follows:
A user boots their Windows 7 SP1 laptop up.
Before Windows login, the user clicks "switch user" and enters their Cisco AnyConnect credentials (this connects OK).
Once the VPN tunnel is established a user logs into Windows.
At this point, 1 of 2 things happen:
1. Most users VPN connection stays connected and user GPO processing\logins work as normal
2. For a minority of users, the VPN connection disconnects and then reconnects. The VPN disconnect and reconnect causes connectivity issues with mapped drives and Outlook (most likely due to GPO processing not applying as the VPN tunnel wasn't established at the required time).
There are no known commanalities between problematic users - all users are in the same OU and laptops are in the same OU, so they should be getting the same AD settings. The same user can login 14 times OK, but may experience this issue on the 15th occasion.
Within the profile xml file (stored in c:\program data\) the key "AutoConnectStart" is set to false for user controllable and default value. The XML policy settings are being applied correctly (we've checked Event ID 3010 within the Cisco AnyConnect Windows logs).
What we have noticed from using the back end Cisco monitoring client is that users who experience connection issues, connect pre windows login OK, but once they're logged into Windows the Cisco VPN AnyConnects seems to try and re-connect, which causes the current VPN tunnel to disconnect and re-connect. This disconnect and re-connect for users seems to cause issues with logon and GPO processing.
So far, the only rock solid way we've found of stopping this disconnect and re-connect behaviour is by configuring a system deny permission on registry key "HKLM\Software\Microsoft\Windows\CurrentVersion\Run". This key contains an entry for Cisco AnyConnect VPN. Unfortunately setting a deny on the individual node value isn't possible and if the key is deleted or modified the system re-creates it. I'd rather avoid setting a system deny on the key for all users.
Any advice on how troubleshoot and diagnose this problem is appreciated.
Thanks

I've attached some log files in case someone is particularly keen eyed at spotting issues (all data is anonymized)
6
Oct 30 2013
10:19:31
172.16.12.17
58124
10.5.128.21
8080
Built inbound TCP connection 123678229 for outside:172.16.12.17/58124 (172.16.12.17/58124)(LOCAL\jpk789) to inside:10.5.128.21/8080 (10.5.128.21/8080)
6
Oct 30 2013
10:19:31
172.16.12.17
58122
10.5.140.210
443
Teardown TCP connection 123678214 for outside:172.16.12.17/58122(LOCAL\jpk789) to inside:10.5.140.210/443 duration 0:00:00 bytes 11971 TCP Reset-O
6
Oct 30 2013
10:19:31
172.16.12.17
51368
10.5.141.155
53
Teardown UDP connection 123678191 for outside:172.16.12.17/51368(LOCAL\jpk789) to inside:10.5.141.155/53 duration 0:00:00 bytes 110
6
Oct 30 2013
10:19:31
172.16.12.17
58123
10.5.12.182
88
Built inbound TCP connection 123678217 for outside:172.16.12.17/58123 (172.16.12.17/58123)(LOCAL\jpk789) to inside:10.5.12.182/88 (10.5.12.182/88)
6
Oct 30 2013
10:19:31
172.16.12.17
62455
10.5.141.155
53
Teardown UDP connection 123678189 for outside:172.16.12.17/62455(LOCAL\jpk789) to inside:10.5.141.155/53 duration 0:00:00 bytes 430
6
Oct 30 2013
10:19:31
172.16.12.17
58122
10.5.140.210
443
Built inbound TCP connection 123678214 for outside:172.16.12.17/58122 (172.16.12.17/58122)(LOCAL\jpk789) to inside:10.5.140.210/443 (10.5.140.210/443)
6
Oct 30 2013
10:19:31
172.16.12.17
56197
10.5.141.155
53
Built inbound UDP connection 123678212 for outside:172.16.12.17/56197 (172.16.12.17/56197)(LOCAL\jpk789) to inside:10.5.141.155/53 (10.5.141.155/53)
6
Oct 30 2013
10:19:31
172.16.12.17
58121
10.5.12.179
389
Built inbound TCP connection 123678196 for outside:172.16.12.17/58121 (172.16.12.17/58121)(LOCAL\jpk789) to inside:10.5.12.179/389 (10.5.12.179/389)
6
Oct 30 2013
10:19:31
172.16.12.17
58120
10.5.12.199
80
Built inbound TCP connection 123678195 for outside:172.16.12.17/58120 (172.16.12.17/58120)(LOCAL\jpk789) to inside:10.5.12.199/80 (10.5.12.199/80)
6
Oct 30 2013
10:19:31
172.16.12.17
51368
10.5.141.155
53
Built inbound UDP connection 123678191 for outside:172.16.12.17/51368 (172.16.12.17/51368)(LOCAL\jpk789) to inside:10.5.141.155/53 (10.5.141.155/53)
6
Oct 30 2013
10:19:31
172.16.12.17
62458
10.5.12.182
389
Built inbound UDP connection 123678190 for outside:172.16.12.17/62458 (172.16.12.17/62458)(LOCAL\jpk789) to inside:10.5.12.182/389 (10.5.12.182/389)
6
Oct 30 2013
10:19:31
172.16.12.17
62455
10.5.141.155
53
Built inbound UDP connection 123678189 for outside:172.16.12.17/62455 (172.16.12.17/62455)(LOCAL\jpk789) to inside:10.5.141.155/53 (10.5.141.155/53)
6
Oct 30 2013
10:19:30
IPSEC: An inbound remote access SA (SPI= 0x67ED9B28) between 80.21.182.245 and 75.12.34.56 (user= jpk789) has been created.
6
Oct 30 2013
10:19:30
IPSEC: An outbound remote access SA (SPI= 0x9C00507E) between 80.21.182.245 and 75.12.34.56 (user= jpk789) has been created.
6
Oct 30 2013
10:19:30
Group User IP <75.12.34.56> AnyConnect session resumed connection from IP <75.12.34.56>.
5
Oct 30 2013
10:19:30
Local:80.21.182.245:4500 Remote:75.12.34.56:62457 Username:jpk789 SA UP. Reason: New Connection Established
4
Oct 30 2013
10:19:30
Local:80.21.182.245:4500 Remote:75.12.34.56:62457 Username:jpk789 Warning Configuration Payload request for attribute 0x7041 could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:19:30
Local:80.21.182.245:4500 Remote:75.12.34.56:62457 Username:jpk789 Warning Configuration Payload request for attribute 0x7040 could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:19:30
Local:80.21.182.245:4500 Remote:75.12.34.56:62457 Username:jpk789 Warning Configuration Payload request for attribute 0x703f could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:19:30
Local:80.21.182.245:4500 Remote:75.12.34.56:62457 Username:jpk789 Warning Configuration Payload request for attribute 0x703e could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:19:30
Local:80.21.182.245:4500 Remote:75.12.34.56:62457 Username:jpk789 Warning Configuration Payload request for attribute 0x703d could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:19:30
Local:80.21.182.245:4500 Remote:75.12.34.56:62457 Username:jpk789 Warning Configuration Payload request for attribute 0x703c could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:19:30
Local:80.21.182.245:4500 Remote:75.12.34.56:62457 Username:jpk789 Warning Configuration Payload request for attribute 0x703b could not be processed. Error: Unknown/Unsupported Attribute
6
Oct 30 2013
10:19:18
172.16.12.17
64287
10.5.12.182
445
Teardown TCP connection 123673186 for outside:172.16.12.17/64287(LOCAL\jpk789) to inside:10.5.12.182/445 duration 0:02:01 bytes 14605 Tunnel has been torn down
6
Oct 30 2013
10:19:17
172.16.12.17
64278
10.5.141.144
445
Teardown TCP connection 123672510 for outside:172.16.12.17/64278(LOCAL\jpk789) to inside:10.5.141.144/445 duration 0:02:15 bytes 9237 Tunnel has been torn down
6
Oct 30 2013
10:19:14
172.16.12.17
64273
10.5.140.231
445
Teardown TCP connection 123672368 for outside:172.16.12.17/64273(LOCAL\jpk789) to inside:10.5.140.231/445 duration 0:02:16 bytes 7297 Tunnel has been torn down
6
Oct 30 2013
10:19:04
172.16.12.17
54449
10.5.141.155
389
Teardown UDP connection 123672541 for outside:172.16.12.17/54449(LOCAL\jpk789) to inside:10.5.141.155/389 duration 0:02:01 bytes 366
6
Oct 30 2013
10:19:04
172.16.12.17
137
10.5.141.155
137
Teardown UDP connection 123672421 for outside:172.16.12.17/137(LOCAL\jpk789) to inside:10.5.141.155/137 duration 0:02:04 bytes 486
6
Oct 30 2013
10:19:00
172.16.12.17
138
10.5.141.155
138
Teardown UDP connection 123672424 for outside:172.16.12.17/138(LOCAL\jpk789) to inside:10.5.141.155/138 duration 0:02:01 bytes 177
6
Oct 30 2013
10:18:58
172.16.12.17
63666
10.5.141.155
389
Teardown UDP connection 123672316 for outside:172.16.12.17/63666(LOCAL\jpk789) to inside:10.5.141.155/389 duration 0:02:01 bytes 366
6
Oct 30 2013
10:18:58
172.16.12.17
53105
10.5.141.155
389
Teardown UDP connection 123672300 for outside:172.16.12.17/53105(LOCAL\jpk789) to inside:10.5.141.155/389 duration 0:02:01 bytes 366
6
Oct 30 2013
10:18:47
172.16.12.17
61715
10.5.12.182
389
Teardown UDP connection 123671945 for outside:172.16.12.17/61715(LOCAL\jpk789) to inside:10.5.12.182/389 duration 0:02:01 bytes 312
6
Oct 30 2013
10:18:43
172.16.12.17
54262
10.5.12.179
389
Teardown UDP connection 123671801 for outside:172.16.12.17/54262(LOCAL\jpk789) to inside:10.5.12.179/389 duration 0:02:01 bytes 355
6
Oct 30 2013
10:18:42
172.16.12.17
57911
10.5.141.156
389
Teardown UDP connection 123671777 for outside:172.16.12.17/57911(LOCAL\jpk789) to inside:10.5.141.156/389 duration 0:02:01 bytes 365
6
Oct 30 2013
10:18:40
172.16.12.17
123
10.5.12.182
123
Teardown UDP connection 123671670 for outside:172.16.12.17/123(LOCAL\jpk789) to inside:10.5.12.182/123 duration 0:02:01 bytes 136
6
Oct 30 2013
10:18:40
172.16.12.17
58107
10.5.12.179
389
Teardown UDP connection 123671639 for outside:172.16.12.17/58107(LOCAL\jpk789) to inside:10.5.12.179/389 duration 0:02:01 bytes 356
6
Oct 30 2013
10:18:40
172.16.12.17
58825
10.5.12.179
389
Teardown UDP connection 123671633 for outside:172.16.12.17/58825(LOCAL\jpk789) to inside:10.5.12.179/389 duration 0:02:02 bytes 355
6
Oct 30 2013
10:18:39
172.16.12.17
60424
10.5.141.156
389
Teardown UDP connection 123671611 for outside:172.16.12.17/60424(LOCAL\jpk789) to inside:10.5.141.156/389 duration 0:02:01 bytes 365
6
Oct 30 2013
10:18:38
172.16.12.17
56635
10.5.141.156
389
Teardown UDP connection 123671566 for outside:172.16.12.17/56635(LOCAL\jpk789) to inside:10.5.141.156/389 duration 0:02:01 bytes 365
6
Oct 30 2013
10:18:38
172.16.12.17
61204
10.5.12.179
389
Teardown UDP connection 123671558 for outside:172.16.12.17/61204(LOCAL\jpk789) to inside:10.5.12.179/389 duration 0:02:01 bytes 355
6
Oct 30 2013
10:18:38
172.16.12.17
50615
10.5.12.179
389
Teardown UDP connection 123671545 for outside:172.16.12.17/50615(LOCAL\jpk789) to inside:10.5.12.179/389 duration 0:02:01 bytes 355
6
Oct 30 2013
10:18:38
172.16.12.17
57940
10.5.141.154
389
Teardown UDP connection 123671537 for outside:172.16.12.17/57940(LOCAL\jpk789) to inside:10.5.141.154/389 duration 0:02:02 bytes 313
6
Oct 30 2013
10:18:38
172.16.12.17
57939
10.5.141.156
389
Teardown UDP connection 123671536 for outside:172.16.12.17/57939(LOCAL\jpk789) to inside:10.5.141.156/389 duration 0:02:02 bytes 366
6
Oct 30 2013
10:18:38
172.16.12.17
64495
10.5.12.182
389
Teardown UDP connection 123671532 for outside:172.16.12.17/64495(LOCAL\jpk789) to inside:10.5.12.182/389 duration 0:02:02 bytes 356
6
Oct 30 2013
10:18:37
172.16.12.17
62965
10.5.12.182
389
Teardown UDP connection 123671521 for outside:172.16.12.17/62965(LOCAL\jpk789) to inside:10.5.12.182/389 duration 0:02:01 bytes 356
6
Oct 30 2013
10:18:37
172.16.12.17
54994
10.5.12.179
389
Teardown UDP connection 123671514 for outside:172.16.12.17/54994(LOCAL\jpk789) to inside:10.5.12.179/389 duration 0:02:01 bytes 356
6
Oct 30 2013
10:18:37
172.16.12.17
54993
10.5.12.179
389
Teardown UDP connection 123671513 for outside:172.16.12.17/54993(LOCAL\jpk789) to inside:10.5.12.179/389 duration 0:02:01 bytes 356
6
Oct 30 2013
10:18:37
172.16.12.17
63390
10.34.140.104
389
Teardown UDP connection 123671483 for outside:172.16.12.17/63390(LOCAL\jpk789) to inside:10.34.140.104/389 duration 0:02:01 bytes 385
6
Oct 30 2013
10:18:37
172.16.12.17
63389
10.33.140.104
389
Teardown UDP connection 123671482 for outside:172.16.12.17/63389(LOCAL\jpk789) to inside:10.33.140.104/389 duration 0:02:01 bytes 384
6
Oct 30 2013
10:18:10
IPSEC: An inbound remote access SA (SPI= 0x5650EE30) between 75.12.34.56 and 80.21.182.245 (user= jpk789) has been deleted.
6
Oct 30 2013
10:18:10
IPSEC: An outbound remote access SA (SPI= 0x42DBDD66) between 80.21.182.245 and 75.12.34.56 (user= jpk789) has been deleted.
6
Oct 30 2013
10:18:10
Group User IP <75.12.34.56> AnyConnect session lost connection. Waiting to resume.
5
Oct 30 2013
10:18:10
Local:80.21.182.245:4500 Remote:75.12.34.56:57103 Username:jpk789 SA DOWN. Reason: peer lost
6
Oct 30 2013
10:17:42
172.16.12.17
64250
10.5.141.186
445
Teardown TCP connection 123671908 for outside:172.16.12.17/64250(LOCAL\jpk789) to inside:10.5.141.186/445 duration 0:00:57 bytes 454851 TCP Reset-I
6
Oct 30 2013
10:17:20
172.16.12.17
137
172.16.13.255
137
Teardown UDP connection 123673268 for outside:172.16.12.17/137(LOCAL\jpk789) to outside:172.16.13.255/137 duration 0:00:00 bytes 0
6
Oct 30 2013
10:17:19
172.16.12.17
137
172.16.13.255
137
Teardown UDP connection 123673244 for outside:172.16.12.17/137(LOCAL\jpk789) to outside:172.16.13.255/137 duration 0:00:00 bytes 0
6
Oct 30 2013
10:17:18
172.16.12.17
137
172.16.13.255
137
Teardown UDP connection 123673218 for outside:172.16.12.17/137(LOCAL\jpk789) to outside:172.16.13.255/137 duration 0:00:00 bytes 0
6
Oct 30 2013
10:16:36
172.16.12.17
63060
10.5.141.155
53
Built inbound UDP connection 123671551 for outside:172.16.12.17/63060 (172.16.12.17/63060)(LOCAL\jpk789) to inside:10.5.141.155/53 (10.5.141.155/53)
6
Oct 30 2013
10:16:36
172.16.12.17
63010
10.5.12.182
88
Built inbound TCP connection 123671549 for outside:172.16.12.17/63010 (172.16.12.17/63010)(LOCAL\jpk789) to inside:10.5.12.182/88 (10.5.12.182/88)
6
Oct 30 2013
10:16:36
172.16.12.17
63009
10.5.12.182
88
Built inbound TCP connection 123671548 for outside:172.16.12.17/63009 (172.16.12.17/63009)(LOCAL\jpk789) to inside:10.5.12.182/88 (10.5.12.182/88)
6
Oct 30 2013
10:16:36
172.16.12.17
63008
10.5.141.156
389
Built inbound TCP connection 123671546 for outside:172.16.12.17/63008 (172.16.12.17/63008)(LOCAL\jpk789) to inside:10.5.141.156/389 (10.5.141.156/389)
6
Oct 30 2013
10:16:36
172.16.12.17
50615
10.5.12.179
389
Built inbound UDP connection 123671545 for outside:172.16.12.17/50615 (172.16.12.17/50615)(LOCAL\jpk789) to inside:10.5.12.179/389 (10.5.12.179/389)
6
Oct 30 2013
10:16:36
172.16.12.17
63007
10.5.12.182
88
Built inbound TCP connection 123671544 for outside:172.16.12.17/63007 (172.16.12.17/63007)(LOCAL\jpk789) to inside:10.5.12.182/88 (10.5.12.182/88)
6
Oct 30 2013
10:16:36
172.16.12.17
55425
10.5.141.155
53
Teardown UDP connection 123671487 for outside:172.16.12.17/55425(LOCAL\jpk789) to inside:10.5.141.155/53 duration 0:00:00 bytes 164
6
Oct 30 2013
10:16:36
172.16.12.17
50614
10.5.141.155
53
Built inbound UDP connection 123671543 for outside:172.16.12.17/50614 (172.16.12.17/50614)(LOCAL\jpk789) to inside:10.5.141.155/53 (10.5.141.155/53)
6
Oct 30 2013
10:16:35
172.16.12.17
56263
10.5.141.156
53
Built inbound UDP connection 123671461 for outside:172.16.12.17/56263 (172.16.12.17/56263)(LOCAL\jpk789) to inside:10.5.141.156/53 (10.5.141.156/53)
6
Oct 30 2013
10:16:35
172.16.12.17
60708
10.5.141.155
53
Built inbound UDP connection 123671460 for outside:172.16.12.17/60708 (172.16.12.17/60708)(LOCAL\jpk789) to inside:10.5.141.155/53 (10.5.141.155/53)
6
Oct 30 2013
10:16:35
172.16.12.17
56982
10.5.141.156
53
Built inbound UDP connection 123671459 for outside:172.16.12.17/56982 (172.16.12.17/56982)(LOCAL\jpk789) to inside:10.5.141.156/53 (10.5.141.156/53)
6
Oct 30 2013
10:16:35
172.16.12.17
64548
10.5.141.155
53
Built inbound UDP connection 123671458 for outside:172.16.12.17/64548 (172.16.12.17/64548)(LOCAL\jpk789) to inside:10.5.141.155/53 (10.5.141.155/53)
6
Oct 30 2013
10:16:35
172.16.12.17
60827
10.5.141.156
53
Built inbound UDP connection 123671457 for outside:172.16.12.17/60827 (172.16.12.17/60827)(LOCAL\jpk789) to inside:10.5.141.156/53 (10.5.141.156/53)
6
Oct 30 2013
10:16:35
172.16.12.17
64207
10.5.141.155
53
Built inbound UDP connection 123671453 for outside:172.16.12.17/64207 (172.16.12.17/64207)(LOCAL\jpk789) to inside:10.5.141.155/53 (10.5.141.155/53)
6
Oct 30 2013
10:16:35
172.16.12.17
137
172.16.13.255
137
Teardown UDP connection 123671443 for outside:172.16.12.17/137(LOCAL\jpk789) to outside:172.16.13.255/137 duration 0:00:00 bytes 0
6
Oct 30 2013
10:16:35
172.16.12.17
137
172.16.13.255
137
Teardown UDP connection 123671442 for outside:172.16.12.17/137(LOCAL\jpk789) to outside:172.16.13.255/137 duration 0:00:00 bytes 0
6
Oct 30 2013
10:16:35
172.16.12.17
137
172.16.13.255
137
Teardown UDP connection 123671441 for outside:172.16.12.17/137(LOCAL\jpk789) to outside:172.16.13.255/137 duration 0:00:00 bytes 0
6
Oct 30 2013
10:16:34
IPSEC: An inbound remote access SA (SPI= 0x5650EE30) between 80.21.182.245 and 75.12.34.56 (user= jpk789) has been created.
6
Oct 30 2013
10:16:34
IPSEC: An outbound remote access SA (SPI= 0x42DBDD66) between 80.21.182.245 and 75.12.34.56 (user= jpk789) has been created.
5
Oct 30 2013
10:16:34
Local:80.21.182.245:4500 Remote:75.12.34.56:57103 Username:jpk789 SA UP. Reason: New Connection Established
4
Oct 30 2013
10:16:34
Local:80.21.182.245:4500 Remote:75.12.34.56:57103 Username:jpk789 Warning Configuration Payload request for attribute 0x7041 could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:16:34
Local:80.21.182.245:4500 Remote:75.12.34.56:57103 Username:jpk789 Warning Configuration Payload request for attribute 0x7040 could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:16:34
Local:80.21.182.245:4500 Remote:75.12.34.56:57103 Username:jpk789 Warning Configuration Payload request for attribute 0x703f could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:16:34
Local:80.21.182.245:4500 Remote:75.12.34.56:57103 Username:jpk789 Warning Configuration Payload request for attribute 0x703e could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:16:34
Local:80.21.182.245:4500 Remote:75.12.34.56:57103 Username:jpk789 Warning Configuration Payload request for attribute 0x703d could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:16:34
Local:80.21.182.245:4500 Remote:75.12.34.56:57103 Username:jpk789 Warning Configuration Payload request for attribute 0x703c could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:16:34
Local:80.21.182.245:4500 Remote:75.12.34.56:57103 Username:jpk789 Warning Configuration Payload request for attribute 0x703b could not be processed. Error: Unknown/Unsupported Attribute
6
Oct 30 2013
10:16:34
Group User IP <75.12.34.56> AnyConnect parent session started.
6
Oct 30 2013
10:16:34
DAP: User jpk789, Addr 75.12.34.56, Connection AnyConnect: The following DAP records were selected for this connection: ContosoPolicy
6
Oct 30 2013
10:16:34
AAA transaction status ACCEPT : user = jpk789
6
Oct 30 2013
10:16:34
AAA retrieved default group policy (DfltGrpPolicy) for user = jpk789
6
Oct 30 2013
10:16:34
AAA retrieved user specific group policy (useGroup1s.Grp) for user = jpk789
6
Oct 30 2013
10:16:34
AAA group policy for user jpk789 is being set to useGroup1s.Grp;
6
Oct 30 2013
10:16:34
AAA user authentication Successful : server = 192.168.7.4 : user = jpk789

After watching a music video or a home movie for a few minutes in my ipad, when i go back to home screen the colors look lighter and weird for some seconds, is that normal? Thanks

IT has happened to me like three times, i use my ipad all day literally and it gets kind of hot, i have tried to take a screen shot to show it but the last time it happened(thethirth time) i was shocked, i wanted this product for so long and if this is a big problem i would be very dissapointed, please help!

Your iPad should not get "kind of hot", but since that is subjective, what is hot to you may not be hot to me. But no matter what, it should not get too hot to hold comfortably. I use my iPad all day long a work and it never gets hot.
If you are getting shocked when you are using the iPad, that doesn't sound normal either. But once again, that is sort of subjective as well.
My suggestion would be to take your iPad to an Apple Store and let an Apple Genius take a look at it just to be sure that there isn't nothing wrong with it. It is still under warranty and if there is a hardware, problem, it can be replaced under the warranty.

Open and closed cursor

I have some doubts/questions .
What is the difference between open and closed cursor?
Are library cache locks same as parse locks?
What is the difference between latch and mutex?
I would be grateful if experts could answer these questions.
Regards

Almost correct. The terminology is however nor correct.
Simplistically:
The SQL engine receives a SQL. It attempts a soft parse first. This means looking for an existing cursor in the Shared Pool with the same SQL. This existing cursor can be in use by other sessions. It does not matter - if that cursor is in used (opend by other sessions), or not. It may not be in use at all and simply sitting there in the cache. If such a cursor is found, it is used for that session's SQL - and that session gets a cursor handle (reference/pointer) to that existing cursor.
If the SQL engine does not find an existing cursor to use, it needs to create a brand new cursor in the Shared Pool. This is a hard parse. Again, the session receives a cursor handle for that new cursor created.
And that is it.
You now need to decide how to use that cursor handle. The cursor itself is a program. You have a handle to execute that cursor program. Via its bind interface you can input data to this cursor program. Then execute it and receive (fetch) output of that cursor program.
So the ideal is to re-use the cursor handle again and again.
Basic example: the following is not optimal as the same cursor is opened and closed, opened and closed, for each read from the file. A lot of soft parsing results.
while not-eof( filehandle )   // read data from a file
read file data into var1, var2
open cursor for 'insert into testtab values( :1, :2)'   // create a cursor
bind cursor :1 = var, :2 = var2 // bind values to cursor (for insert)
exec cursor // do SQL insert
close cursor
end whileThis is a lot better. A single cursor is used and executed again and again:
open cursor for 'insert into testtab values( :1, :2)'   // create a cursor
while not-eof( filehandle )   // read data from a file
read file data into var1, var2
bind cursor :1 = var, :2 = var2 // bind values to cursor (for insert)
exec cursor // do SQL insert
end while
close cursor In this case a single soft/hard parse - and the client uses that cursor handle to execute that cursor (insert data) program again and again.

Opening and Closing Balances -SAP

Hi experts
please explain me about the Opening and Closing Balance in SAP? and what is the use of Opening and closing Balance?
regards
anand

Hi Ananda
opening balance : when ever u run any financial report for example a ledger profit and loss account then it has a opening balance and a closing balance
say for example if we see the balance of our cash account in sap at end of the day today then we can consider the balance as x amount as closing balance and when again tomorrow there is some transaction in the same account than this x Amount is considered as the opening balance for tomorrows date
Hope this would suffice your Concern
Regards,
Manish

Opening and closing Access database in a loop causes an Error.

I am loading test conditions from an Access DB in a multiple nested loop. The loops successively drill into the DB. ei Temperature, Humidity, Power. Consequently the DB is opened and closed numerous (2000) times. The Errors returned are(-2147467259) Unspecified Error or (2147024882) System Resources low. I have disabled result recording in the edit sequence properties dialog. I do see a constant memory consumption, but of 128MB, it never gets below 40MB. I have enclosed the example sequence file I am using.
Attachments:
Open-Close.seq ‏35 KB

Jacy,
"jacy" wrote in message
news:[email protected]..
> I am loading test conditions from an Access DB in a multiple nested
> loop. The loops successively drill into the DB. ei Temperature,
> Humidity, Power. Consequently the DB is opened and closed numerous
> (2000) times. The Errors returned are(-2147467259) Unspecified Error
> or (2147024882) System Resources low. I have disabled result recording
> in the edit sequence properties dialog. I do see a constant memory
> consumption, but of 128MB, it never gets below 40MB. I have enclosed
> the example sequence file I am using.
I've seen problems with OLEDB (which I assume TestStand used behind the
scenes) with Access and SQL where rapid opening/closing of the sam
e source
(database) can generate errors. I don't know for sure, but I assume that
the changes from the last close are not fully propogated before the next
open is processed.
Getting back to TestStand, if all the tables you're querying are in the same
database, then you should just open the database once at the beginning and
close it at the end. Then do seperate table open/closes between the
database open/close.
Bob.

Ipod generation 1 apps opening and closing instantly with software version

I have a Ipod Touch generation 1 and have just downloaded version 3.1.3 upgrading from 1.1.5. I am now having a problem with all the apps that I have downloaded from the App store through the IPOD. The apps are opening and closing instantly.
Any comments?
Thank you for any advise and or help!

By a reset, I believe he is referring to holding down the Home button and the Sleep button both at the same time until the apple logo appears on the screen. Ignore the "slide to power off" option that might come up. This process generally takes about 5-15 seconds to see the logo, then about another minute or so after that for the reset to complete.
Now, as for the issue you are seeing, if the reset doesn't resolve it, it might be the same thing I have seen on other iPods. Almost all (if not all) I have seen with this problem have been when the owner unplugged the iPod from their computer before the sync process had fully completed. This seems to leave the iPod app directory structure in some "confused state". Every time I have seen this happen, I have been able to resolve the issue by deleting an app from the device, then re-downloading it using the App Store app on the iPod (while connected to a wifi network). To play it safe, I generally use a free app.
Don't ask me why, but the downloading of an app directly from the device itself seems to reset the iPod app structure and the other apps generally resume wirking properly...

Service Requests Open 5 days?/Service Requests Open and Closed Today

Help!
How would I determine service requests open greater then 5 days, I use the # of Open SR's but cannot seem to get a date to work.
Also what is the best way to count the SR's open and closed on the same day?
Thanks in advance.

You need to include a TIMESTAMPDIFF function in your filter... something to the effect of
TIMESTAMPDIFF(SQL_TSI_DAY,"Service Request"."Create Date",CURRENT_DATE) > 5
Double check the column reference.
Mike L

Restrict the posting period opening and closing for some users

Similar Messages

Maybe you are looking for