Creation of appointments within undefined timeslots

[Former Member]

Hello,

I am posting a new tread as I seem to be missing some info (perhaps I missed it). In our system we are able to post new appointments (for both Patient types) in areas that have not been defined as open in our planing grid (for sample a Sunday while working days are excluded in that period). Using NR16 this can happen if the field schedualing type is filled. Is there any way to block agents from creating appointments in non defined timeslots?

I strongly suspect a customizing point but I don't seem to find it.

Any help again appreciated.

Reg Daniel.

[Claudius]

Hi Daniel,

please check out the [documentation|http://help.sap.com/saphelp_erp60_sp/helpdata/en/08/ac8669d46711d189f20000e829fbbd/content.htm]. Somewhere in the middle of that document you'll find:

You can schedule outpatient visits as you like, irrespective of whether time slots are available or not, or whether a time slot is open or booked. This means you can also create an outpatient visit for a period defined as a break or outside of the working/consulting hours. It is only impossible to create provisional appointments or outpatient visits for time slots for which a planning block is set by means of the scheduling type.

So I guess you have to make use of the planning block in case the color codes alone do not refrain users from picking such unwanted slots.

Best regards

Claudius

[Former Member · Accepted solution]

Daniel,

We solved this issues with the object of authorization N_AMB_DSP (IS-H: Authorization Visit Scheduling).

Activity:

01 Create or generate

02 Change

03 Display

06 Delete

O1 Overbook

IS-H: Business Partner (Author: *

IS-H: Key of Building Unit (Au: *

IS-H: Scheduling Type for Visi: *

IS-H: Institution (Authorizati: (Your Institution or *)

IS-H: Identification Key of Or: *

With different combinations achievement variants very powerful.

Best regards,

Alberto

[Former Member]

Hi Alberto yes tried the solution you mentioned but we are unable to define the time slots to be cancelled from the ones that are valid. I also tried Claudius solution, but people are able to modified blocked Scheduling Type as a user has the possibility to change it. We have in our system users that are cross buisiness, so in our system there is not possible block or use an authorization objet on that precise field. therefore any user can created appointments on blocked zones. Any other clues? Thanks in Advance.

[Claudius]

Hi Daniel,

I would have thought that a productive client is locked for changes in customizing, isn't that the case here? Then normal users could not simply change the attributes of a disposition type.

But at the end I think a planning tool can only support an organization, but not really force users to comply with business rules like "do not offer appointments on Sundays". I would have thought that by using a set of well defined disposition types (including the ones with a explicit block) it should be possible even for planners responsible for many departments to adhere to the rules as they are "visible" in the calendar.

Regards

Claudius

[Former Member]

Claudius,

Sorry for the late reply, of course the system is blocked in Production on the customizing side. Now the matter occurs when a user decides to place an appointement in grey or red areas of the planning (he or she can create an appointment by placing a visit type). I am looking into the lead that Alberto has pointed out to see if that manages it (on the autorization side)? As we have hundreds of users a fonctional rule "not to do" is not applicable.

[Claudius]

Hi Daniel,

so why do you think the solution with the planning block I described early would not work? From my perspective there are two alternatives:

1.) Make users aware of the consequences if they make appointments in "gray or red" time slots through training and organizational procedures

2.) If that doesn't help, configure the system such that those time slots cannot be picked by users using the planning block.

Question to all readers: has anybody solved this issue differently? Please let us know!

Regards

Claudius

[Former Member]

Claudius,

For point 1) no as I described earlier, there's hundreds of users in the system creating thousands of appointments. Client wants to make sure there is no illicit use.

for point 2) there's too many OU and doctors in the system to create them, so this solution is not applicable (too many exceptions, client is supposed to create the valid planning areas only).

Again, thanks,

Daniel.

[Claudius]

Daniel,

I have spoken to one of our experts in development and he thinks that using authorities should prevent users from making appointments into "gray" or "red" areas.

Please take a look at authorization object N_AMB_DSP. Activities 'O1' and 'O2' (Overbooking and Force In) is necessary to book into such areas.

Please let us know, whether this works.

Best regards

Claudius

Edited by: Claudius Metze on Apr 17, 2008 9:55 AM