Skip to content

Book, change and delete days

How-to guide

Two verbs cover most bookings:

  • set makes the given days contain exactly one item: whatever was booked on them is deleted first, then the item is created, all in one batch. Use it when you want a day to be something.
  • fill adds an entry next to what is already there. Use it to top a day up.

Both take one day, several days, or a range whose working days are expanded. Both accept a favorite instead of an item. Hours default to the favorite’s, otherwise 8.

Set the 15th to a full day of holiday. Dry run first.

std_set {dates: ["2026-09-15"], item: {attendanceType: "0010"}, hours: 8, dryRun: true} shows what would be removed and created. Then the same call without dryRun.

Put the 8th to the 12th on the NovaLabs order, 8 hours a day, short text “NovaLabs”.

std_set {dates: ["2026-09-08", "2026-09-09", "2026-09-10", "2026-09-11", "2026-09-12"], item: {order: "900140", attendanceType: "0081"}, hours: 8, shortText: "NovaLabs"}

Book the 16th and 17th on the Globex sales order, chargeable.

std_set {dates: ["2026-09-16", "2026-09-17"], item: {salesOrder: "3141993", salesOrderItem: "000401", attendanceType: "0800"}}

Book the 18th from my Holiday favorite.

std_set {dates: ["2026-09-18"], favorite: "Holiday"}

Add 2 hours of administration on the 19th, keep the rest.

std_fill {dates: ["2026-09-19"], item: {attendanceType: "0077"}, hours: 2}. std_fill also takes notes (long text) and a favorite.

You need the entry’s counter, shown by std entries / std_entries and by std days.

Change entry 000054851366 on the 19th to 4 hours of administration.

std_update {counter: "000054851366", date: "2026-09-19", item: {attendanceType: "0077"}, hours: 4}

Delete entries 000054598801 and 000054598802.

std_remove {counters: ["000054598801", "000054598802"]}. The entries must lie within from / to, which default to the current month.

Entries are released on save; --no-release / release: false omits the flag. On profiles that approve directly (BearingPoint’s MA-FACHL) the entry is approved on save either way, so the flag changes nothing visible there. See Timesheet concepts.

The result lists each day with ok, the counter of the created entry and, on failure, SAP’s reason. When any day was rejected the CLI exits with code 4 and the MCP tool returns isError, but the days that succeeded stay booked. Closed periods are refused up front.