Functionality
This BAPI enables you to create business hours for a business partnerentered in the parameter BUSINESSPARTNER.
The schedule type of the business hours, which can be mapped to complexsets of rules by means of individual rules or links between theserules, is enteredin the parameter SCHEDULE_TYPE. Calling hours, goods receiving hoursor visiting hours, which can be identified in each case by means ofan ID, are examples of schedule types.
You can create a set of rules (of any required complexity) of businesshours for each schedule type.
The tables COMBINEDRULE, DAILYRULES, WEEKLYRULES etc. contain thedata that is valid for each rule type, and the corresponding linkinformation. You can define link rules for daily, weekly and monthlybusiness hours, as well as those that take place on fixed dates.
After it has been checked that the business partner exists, theschedule type and the data for the rules are checked for consistency andvalidity. Any errors that may occur are logged, and issued in thetable RETURN.
If the result of the check is negative, the business hours are notcreated.

Notes
If business hours already exist for the schedule type, they are over
written with the new data.

Description
Key that identifies a business partner unambiguously per client.

Description
Key that identifies a schedule type.
Example: Calling hours (A), goods receiving hours (B) orvisiting hours (C).

Value range
The schedule types are defined in table TB049.

Description
Link rule (R rule) for summarizing a set of rules consisting ofindividual rules of the types D (daily rule), W (weekly rule), M(monthly rule) and T (rule for fixed appointments).
If the business hours of a schedule type (calling or visiting hours)consist of several individual rules, these individual rules aregrouped together in a link rule. The individual rules contained withinthe R rule are referenced by means of their rule ID, whereby thehighest-level R rule, as the parent rule for the overall rule, containsthe relevant data for validity, conflicts (behavior on non-workingdays), and the public holiday or factory calendar used.
An R rule is either of the type RO or RN. R rules of the type ROlink individual rules on the basis of the logical OR, while those of thetype RN make the link on the basis of the logical NOT.
This means that calling hours, for example, that occur on certain,pre-determined days are mapped by means of an RO rule and an individualrule of the type T (fixed appointment). Fixed times that do NOT occuron certain days, are mapped by means of an RN rule together with aT rule, on the other hand.
An R rule can contain up to eight individual rules that can beidentified by means of their rule ID. All rule types can be used,including other R rules. In this way it is possible to map rules ofunrestricted complexity.
It does not make sense to have an R rule without individual rules.
Parameter fields
RULE_ID,,,,Rule ID of the link rule
TYPE,,,,,,Type of the link rule
START_DATE,,Overall rule valid from
END_DATE,,,,Overall rule valid to
CONFLICTS,,,,Exceptions
FCALID,,,,Factory calendar
HCALID,,,,Public holiday calendar
RULEID1-,,,,Rule IDs of the individual rules to be linked, or additionalR rules
RULEID8
Factory and public holiday calendars may not be entered at the sametime.

Value range
TYPE,,,,,,RO, RN
CONFLICTS,,,,SPACE, 0 ,,Appointment takes place even if the dateoccurs on a non-working day, according to the factory or public holidaycalendar used.
,,,,,,K ,,,,Appointment is cancelled on non-working days
,,,,,,+, - ,,,,Appointment is moved by one day to the next (+) orprevious (-) working day.

Description
A daily rule (type D) contains data for daily occurring business hoursof a schedule type (calling or visiting hours).
An overall rule consisting of several individual rules grouped togetherby means of a link rule (R rule), can contain any number of rules ofone type.
In this way, business hours with different recurrences are mapped bymeans of several D rules.
If, for example, calling hours take place every day between 9:30and 10:30, and every 3 days between 15:45 and 17:00, then two dailyrules with the relevant data are transferred.
Rules consisting of more than one individual rule, regardless of thetype, should be grouped together by means of a link rule. In this caseit is not necessary to enter a validity period, conflicts, and a factoryor public holiday calendar, since this information should be assignedto the link rule. If, on the other hand, the rule consists of anindividual rule, this information should be entered.
Parameter fields
RULE_ID,,,,Rule ID of the rule
TYPE,,,,,,Type of the rule
START_DATE,,Valid from
END_DATE,,,,Valid to
CONFLICTS,,,,Exceptions
FCALID,,,,Factory calendar
HCALID,,,,Public holiday calendar
DAYS,,,,,,Recurrence in days; number of days between the appointments
TIME_FROM,,Start time
TIME_TO,,,,End time
Factory and public holiday calendars may not be entered at the sametime.

Value range
TYPE,,,,,,D
CONFLICTS,,,,SPACE, 0 ,,Appointment takes place even if the dateoccurs on a non-working day, according to the factory or public holidaycalendar used.
,,,,,,K ,,,,Appointment is cancelled on non-working days
,,,,,,+, - ,,,,Appointment is moved by one day to the next (+) orprevious (-) working day.

Description
A fixed rule (type T) contains data for business hours of a scheduletype (calling or visiting hours) that either take place (additionally)or do not take place.
Whether or not a fixed appointment is cancelled (that it, does not takeplace) or not, is detemined by the combination of the T rule with alink rule of the type RN (appointment is cancelled) or RO (appointmenttakes place additionally).
It does not make sense to have a T rule without a relevant link rule.
An overall rule consisting of several individual rules grouped togetherby means of a link rule (R rule) can contain any number of rules of onetype.
If, for example, additional calling times for the 23.12 of a year shouldtake place from 11.00 to 12.00, but not from 02.01 to 04.01, then aT rule together with an R rule that references this rule of the type ROshould be created, as well as a T rule together with an R rule thatreferences this rule of the type RN.
Rules consisting of more than one individual rule, regardless of thetype, should be grouped together by means of a link rule. In this caseit is not necessary to enter a validity period, conflicts, and a factoryor public holiday calendar, since this information should be assignedto the link rule. If, on the other hand, the rule consists of anindividual rule, this information should be entered.
Parameterfelder
RULE_ID,,,,Rule ID of the rule
TYPE,,,,,,Type of rule
START_DATE,,Valid from
END_DATE,,,,Valid to
CONFLICTS,,,,Exceptions
FCALID,,,,Factory calendar
HCALID,,,,Public holiday calendar
YEAR_FROM,,Year
MONTH_FROM,,Month
DAY_FROM,,,,Day
TIME_FROM,,Start time
YEAR_TO,,,,Year
MONTH_TO,,,,Month
DAY_TO,,,,Day
TIME_TO,,,,End time
Factory and public holiday calendars may not be entered at the sametime.

Value range
TYPE,,,,,,T
CONFLICTS,,,,SPACE, 0 ,,Appointment takes place even if the dateoccurs on a non-working day, according to the factory or public holidaycalendar used.
,,,,,,K ,,,,Appointment is cancelled on non-working days
,,,,,,+, - ,,,,Appointment is moved by one day to the next (+) orprevious (-) working day.

Description
A monthly rule (type M1) contains data for monthly business hours of aschedule type (calling or visiting hours), whereby the business hoursoccur in a defined monthly time period on a certain day of the month.
An overall rule that consists of several individual rules groupedtogether by means of a link rule (R rule), can contain anynumber of rules of one type.
Thus business hours can be mapped in different monthly intervalson different days of the month via several rules of the type M1.
If, for example, visiting hours should take place an the first day ofeach month between 9.30 and 11.00, and every three months on thefifteenth day from 13.30 to 15.30, then two monthly rules of the typeM1 are transferred with the relevant dates: one monthly rule with thetime period 1 and the day 1, and another monthly rule with the timetime period 3 and the day 15.
Rules consisting of more than one individual rule, regardless of thetype, should be grouped together by means of a link rule. In this caseit is not necessary to enter a validity period, conflicts, and a factoryor public holiday calendar, since this information should be assignedto the link rule. If, on the other hand, the rule consists of anindividual rule, this information should be entered.
Parameter fields
RULE_ID,,,,Rule ID of the rule
TYPE,,,,,,Type of rule
START_DATE,,Valid from
END_DATE,,,,Valid to
CONFLICTS,,,,Exceptions
FCALID,,,,Factory calendar
HCALID,,,,Public holiday calendar
DAYS,,,,,,Day of the month
MONTH,,,,Monthly recurrence
TIME_FROM,,Start time
TIME_TO,,,,End time
Factory and public holiday calendars may not be entered at the sametime.

Value range
TYPE,,,,,,M1
CONFLICTS,,,,SPACE, 0 ,,Appointment takes place even if the dateoccurs on a non-working day, according to the factory or public holidaycalendar used.
,,,,,,K ,,,,Appointment is cancelled on non-working days
,,,,,,+, - ,,,,Appointment is moved by one day to the next (+) orprevious (-) working day.
DAYS,,,,,,[1..31]

Default

Description
A monthly rule (type M3) contains data for monthly business hours of aschedule type (calling or visiting hours), whereby the business hoursrecur on a certain day of the month, at certain monthly intervals.
An overall rule that consists of several individual rules groupedtogether by means of a link rule (R rule), can contain any numberof rules of one type.
Thus business hours can be mapped in different monthly intervalson different days of the month via several rules of the type M3.
If, for example, visiting hours should take place an the second Tuesdayof a month from 9.30 to 11.00, and every 2 months on the firstMonday of the month from 13.30 to 15.30,then two monthly rules of the type M3 are transferred with the relevantdata: one monthly rule with the period factor 2 (referring to Tuesday,the second day of the week), and a period factor 1 (referring to therecurrence every month); and another monthly rule with the period factor1 (referring to the first day of the week), and a period factor of 2(referring to the recurrence every second month).
Rules consisting of more than one individual rule, regardless of thetype, should be grouped together by means of a link rule. In this caseit is not necessary to enter a validity period, conflicts, and a factoryor public holiday calendar, since this information should be assignedto the link rule. If, on the other hand, the rule consists of anindividual rule, this information should be entered.
Parameter fields
RULE_ID,,,,Rule ID of the rule
TYPE,,,,,,Type of rule
START_DATE,,Valid from
END_DATE,,,,Valid to
CONFLICTS,,,,Exceptions
FCALID,,,,Factory calendar
HCALID,,,,Public holiday calendar
DAY_NR,,,,Recurrence of the weekday
WEEKDAY_NR,,Number of the weekday
MONTHS,,,,Monthly recurrence
TIME_FROM,,Start time
TIME_TO,,,,End time
Factory and public holiday calendars may not be entered at the sametime.

Value range
TYPE,,,,,,M3
CONFLICTS,,,,SPACE, 0 ,,Appointment takes place even if the dateoccurs on a non-working day, according to the factory or public holidaycalendar used.
,,,,,,K ,,,,Appointment is cancelled on non-working days
,,,,,,+, - ,,,,Appointment is moved by one day to the next (+) orprevious (-) working day.
DAY_NR,,,,[1..5]
WEEKDAY_NR,,[1..7]

Description
This table contains confirmations from the method call.

Description
A weekly rule (type W) contains data for the business hours of aschedule type (calling or visiting hours) that recur weekly.
An overall rule that consists of several individual rules groupedtogether by means of a link rule (R rule), can contain any numberof rules of one type.
Thus business hours that recur at differentweekly intervals or on different days of the monthcan be mapped via several rules of the type W.
If, for example, visiting hours should take place every Monday andWednesday from 8.00 to 9.30, and every 2 weeks on WednesdayMonday of the month from 16.15 to 17.30,then two weekly rules are transferred with the relevantdata: one weekly rule with the period factor 1 (for weekly recurrence)and the days Monday and Wednesday, and another weekly rule with theperiod factor 2 (for fortnightly recurrence) and the day Wednesday.
Rules consisting of more than one individual rule, regardless of thetype, should be grouped together by means of a link rule. In this caseit is not necessary to enter a validity period, conflicts, and a factoryor public holiday calendar, since this information should be assignedto the link rule. If, on the other hand, the rule consists of anindividual rule, this information should be entered.
Parameter fields
RULE_ID,,,,Rule ID of the rule
TYPE,,,,,,Type of rule
START_DATE,,Valid from
END_DATE,,,,Valid to
CONFLICTS,,,,Exceptions
FCALID,,,,Factory calendar
HCALID,,,,Public holiday calendar
WEEKS,,,,Recurrence in weeks
MONDAY-,,,,Indicator for the active day in the week rule
SUNDAY
MONDA_FROM-,,Start time for the respective active day in the week rule
SUNDA_FROM
MONDAY_TO-,,End time for the respective active day in the week rule
SUNDAY_TO
Factory and public holiday calendars may not be entered at the sametime.

Value range
TYPE,,,,,,W
CONFLICTS,,,,SPACE, 0 ,,Appointment takes place even if the dateoccurs on a non-working day, according to the factory or public holidaycalendar used.
,,,,,,K ,,,,Appointment is cancelled on non-working days
,,,,,,+, - ,,,,Appointment is moved by one day to the next (+) orprevious (-) working day.
WEEKS,,,,[1..10]