Revenue from Contract with Customer Performance Obligations (Details) - USD ($) $ in Millions	12 Months Ended
	Dec. 31, 2020	Dec. 28, 2019
Revenue Recognition [Line Items]
Revenue [Policy Text Block]	We enter into contracts with customers that may include various combinations of our software solutions and related services, which are generally capable of being distinct and accounted for as separate performance obligations. Performance obligations that are not distinct at contract inception are combined. Contracts that include software customization may result in the combination of the customization services with the software license as one distinct performance obligation.The predominant model of customer procurement involves multiple deliverables and includes a software license agreement, project-related implementation and consulting services, software support, hosting services, and computer hardware. We allocate revenues to each performance obligation within an arrangement based on estimated relative stand-alone selling price. Revenue is then recognized for each performance obligation upon transfer of control of the software solution or services to the customer in an amount that reflects the consideration we expect to receive.
Revenue, Remaining Performance Obligation, Amount	$ 13,040	$ 13,710
Revenue, Remaining Performance Obligation, Expected Timing of Satisfaction, Explanation	we expect to recognize approximately 30% of the revenue over the next 12 months and the remainder thereafter
Perpetual Software Licenses [Member]
Revenue Recognition [Line Items]
Revenue, Performance Obligation, Description of Timing	Perpetual software licenses - We recognize perpetual software license revenues when control of such licenses are transferred to the client ("point in time"). We determine the amount of consideration allocated to this performance obligation using the residual approach
Software as a Service [Member]
Revenue Recognition [Line Items]
Revenue, Performance Obligation, Description of Timing	Software as a service - We recognize software as a service ratably over the related hosting period ("over time")
Time-based Software and Content License Fees [Member]
Revenue Recognition [Line Items]
Revenue, Performance Obligation, Description of Timing	Time-based software and content license fees - We recognize a license component of time-based software and content license fees upon delivery to the client ("point in time") and a non-license component (i.e. support) ratably over the respective contract term ("over time")
Remote Hosting Recurring Services [Member]
Revenue Recognition [Line Items]
Revenue, Performance Obligation, Description of Timing	Hosting - Remote hosting recurring services are recognized ratably over the hosting service period ("over time"). Certain of our hosting arrangements contain fees deemed to be a "material right" under Topic 606. We recognize such fees over the term that will likely affect the client's decision about whether to renew the related hosting service ("over time")
Services [Member]
Revenue Recognition [Line Items]
Revenue, Performance Obligation, Description of Timing	Services - We recognize revenue for fixed fee services arrangements over time, utilizing a labor hours input method. For fee-for-service arrangements, we recognize revenue over time as hours are worked at the rates clients are invoiced, utilizing the "as invoiced" practical expedient available in Topic 606. For stand-ready services arrangements, we recognize revenue ratably over the related service period
Support and Maintenance [Member]
Revenue Recognition [Line Items]
Revenue, Performance Obligation, Description of Timing	Support and maintenance - We recognize support and maintenance fees ratably over the related contract period ("over time")
Hardware [Member]
Revenue Recognition [Line Items]
Revenue, Performance Obligation, Description of Timing	Hardware - We recognize hardware revenues when control of such hardware/devices is transferred to the client ("point in time")
Transaction Processing [Member]
Revenue Recognition [Line Items]
Revenue, Performance Obligation, Description of Timing	Transaction processing - We recognize transaction processing revenues ratably as we provide such services ("over time")